list_stores

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

Annotations already establish readOnlyHint=true, so the safety profile is covered. The description adds meaningful non-obvious context — full directory for DK but only curated grocery chains for NO/SE/FI — which an agent could not infer from the schema. It does not mention result ordering or pagination, which keeps it short of 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?

Front-loaded purpose sentence followed by labeled USE WHEN / NOT FOR clauses and a return-shape note. Every sentence carries distinct routing or coverage information, with no filler.

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?

Covers purpose, country scope, the per-country coverage asymmetry, downstream consumers, and exclusions. For a two-parameter read-only listing tool with no output schema, nothing an agent needs to select or call it correctly is missing.

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%, with 'all' and 'query' both documented in the schema, so the baseline is 3. The description adds no parameter-level detail beyond what the schema already provides.

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 grocery chains with dealer IDs') plus the scope constraint that defines the result set (DK/NO/SE/FI). It clearly separates itself from siblings like search_deals and get_store_offers without needing the 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?

Explicit USE WHEN names two concrete downstream consumers (get_store_offers, update_household), and an explicit NOT FOR clause redirects to search_deals and deals_this_week. Both the when and the when-not are spelled out with alternatives.

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