List stores

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

Annotations already declare readOnlyHint and destructiveHint false, covering safety. The description adds minimal behavioral context beyond the returned addresses and downstream use. No pagination or rate-limit detail is provided, but the annotation bar lowers the need.

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 with no filler. The main action and output are front-loaded, and the second sentence adds high-value downstream usage context in few words.

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 list tool with no output schema, it gives the core purpose and usage context but omits parameter semantics and any response shape or pagination notes. An agent would need to infer or probe the behavior of store_ids and show_deleted.

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 0%, so the description must compensate for parameter meaning. It does not mention how store_ids filters results or what show_deleted does, leaving the agent to guess from property names alone.

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 stores on the account') with output detail ('with their addresses'). The plural scope and mention that other filters use store_id from here clearly distinguish it from the singular get_store tool.

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 provides clear contextual guidance: this is the source of store_ids for filters elsewhere. It does not explicitly name alternatives or state when not to use it, but the implied use case is strong.

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