Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full behavioral burden. It discloses the result shape ('type' field, slug, focus, and price) and even points to the external source for current prices, giving agents a realistic picture of what a successful call returns.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is three sentences and front-loads the core action plus marketplace context. The examples and price details are mildly verbose but earn their place because they clarify the type taxonomy and the external pricing caveat.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description compensates by describing result fields and the pricing data source. It gives enough context for an agent to invoke the tool correctly, though it does not describe ordering, empty-result behavior, or when to prefer get_persona_details.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 75%, so the schema already documents query, type, and category. The description adds semantic depth by explaining what each product type means, how the type filter values map to marketplace concepts, and what fields like focus and slug represent.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with the concrete action 'Search the authority.md marketplace' and then clarifies what lives there by naming the three product types with examples. This clearly distinguishes search_personas from the sibling tools that fetch details, list categories, or purchase.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly says to use the tool when the user asks about a specific person, category, task, or recommendation. It does not explicitly state when not to use it or name alternative sibling tools, but the usage context it provides is clear and actionable.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.