list_stores

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

With no annotations at all, the description carries the full disclosure burden and largely drops it: it does not state that this is a read-only operation, whether the full set of configured stores is returned or paginated, or what happens when none exist. Only the mention of descriptive fields gives any behavioral hint, and that mostly duplicates the output 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?

Two very short clauses with no wasted words, and the resource identity is front-loaded. The trailing pointer about the `key` field is terse to the point of being cryptic, but the overall size is appropriate for a trivial no-arg lookup.

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?

An output schema exists, so return-value explanation is not required, and a zero-parameter tool is inherently simple. However, with no annotations the description should have stated the read-only nature and whether the list is complete or paginated; those omissions leave a modest but real gap.

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 there is nothing for the description to disambiguate beyond the schema. The note about the `key` field usefully tells the agent how to consume results elsewhere, which adds a small amount of semantic value.

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 names the resource ('Stores configured by the user') and its identifying fields (chain, store code, name), but never states an explicit verb such as 'list' or 'returns'. An agent can infer enumeration from the tool name, but the description itself is a noun phrase rather than a clear action statement.

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 only guidance is 'Use the `key` field elsewhere', which hints at cross-referencing results but never says when to call this tool or what it replaces. No alternatives or exclusions are given, and the listed siblings (search_products, optimize_basket) are not addressed, leaving the agent to infer that this is a prerequisite lookup.

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