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

readOnlyHint=true already declares the safety profile, so the description's added value is its disclosure of return content — ids and addresses — which annotations do not cover and which is important since there is no output schema. It also anchors the tool to a concrete API surface ('Current RMS: GET /stores'). No rate limits or auth notes, but for a trivial read that is acceptable.

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?

A single dense sentence front-loads the action and resource, then appends the payoff (the store_id needed downstream) and the API mapping. No filler and nothing repeated from the annotations.

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 with no output schema, the description supplies exactly what would otherwise be missing: the return shape (ids and addresses) and the downstream purpose. Nothing an agent needs to call it correctly is absent.

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 there is nothing for the description to disambiguate. The mention of returning ids is a natural extra, not a parameter concern.

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 account's stores') plus a clarifying gloss ('warehouses/depots'), which disambiguates the domain term. It also names what is returned (ids and addresses), so an agent can distinguish it from sibling list tools like list_products or list_members without opening any schema.

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?

Explicitly gives the selecting condition: this is 'needed for store_id when creating an opportunity', which routes the agent from current_rms_create_opportunity to this tool. It stops short of stating exclusions or alternatives, but the trigger context 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.