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

Annotations already declare readOnlyHint=true, so the safety profile is covered. Beyond that, the description adds valuable behavioral context by listing the returned fields and mentioning pagination via next_after, though it does not discuss auth, rate limits, or the deleted-record behavior covered by the schema.

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 short, front-loaded, and structured as an imperative list of what is returned, how it is used, and how to paginate. No sentence feels wasted or buried.

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?

For a simple read-only list tool with annotations covering safety and a fully documented schema, the description provides enough context: returned fields, pagination cue, downstream use, and endpoint. It is slightly less complete because it does not mention optional deleted-record handling, but that is well covered by the schema.

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 description coverage is 100%, so all four pagination-related parameters are already documented in detail. The description only briefly mentions 'Paginate with next_after', which does not add meaningful semantics beyond the schema's own cursor instructions.

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 gives a specific verb and resource ('List the store's outlets (locations)') and even enumerates returned fields and the endpoint. It is clearly distinguishable from the singular sibling 'get_outlet' because it describes enumeration rather than retrieval of one outlet.

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?

It provides useful context by explaining that the returned outlet id should be used to filter sales, stock and stock orders. However, it does not explicitly state when to use this instead of the sibling 'get_outlet', so the alternative-selection guidance is only implied.

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