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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered. The description adds genuine value beyond that by listing the response fields (compensating for the missing output schema) and disclosing the underlying endpoint 'GET /stores'; it does not mention pagination or auth, hence not a 5.

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?

Two short sentences, zero filler, with the core purpose and returned fields front-loaded before the downstream-usage hint. Every clause earns its place.

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 parameterless read tool with no output schema, the description supplies what matters: what is returned and how the ids are consumed elsewhere. Only minor gaps remain (whether the full account store list is always returned, pagination), which are unlikely to block correct invocation.

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?

The tool takes zero parameters, so per the baseline this scores 4. The description correctly implies no filtering or scoping inputs are required.

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?

States a specific verb and resource ('List the shops (stores) of the account') and enumerates the returned fields (id, name, warehouse id, currency, time zone, address), so the agent knows exactly what it gets. No sibling tool lists stores, so there is little ambiguity, though it does not explicitly distinguish itself from the nearby list_warehouses tool despite mentioning warehouse id.

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?

'Use store ids for sales, payment types and reports' tells the agent this is a prerequisite lookup whose ids feed downstream tools, which is real usage context rather than an implied one. There is no alternative tool to exclude, so the absence of explicit when-not guidance costs little.

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