Here's what I'm thinking about this week: I've said this already, but I keep coming back to it: agent experience is an extension of developer experience. (Or builder experience, however your org thinks about it.)
Yes, agents need distinct things. We know some of them, and we are still discovering others. And what agents need is a moving target as models and harnesses evolve.
But what is not a moving target is the need to understand the actual developers who are building with your product. They may be using agents to do the implementation, but the developer needs drive those sessions. If you do not have and communicate a clear understanding of who the developers are who are building with your product, what tasks they need to perform, and how your product serves those tasks, no amount of agent experience work is going to help you.
If you don't have a clear narrative for agents to understand in the context of developer goals, agents won't select your product. Period.
So all of the very hard, unglamorous product work of understanding your developers - personas and the jobs they need to do - is a prerequisite for agent experience measurement and improvement.
Yes, you can implement static checks that say whether an agent can read your documentation. But a documentation site that scores 100 in AFDocs but doesn't have what agents need to understand and use your product isn't going to get it selected. Appearing in directories and marketplaces doesn't mean agents will choose you.
DX first, then AX. Start with DX.