list_stores

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

With no annotations, the description carries full burden. It discloses the tool returns store names and dealer IDs, and importantly differentiates behavior per country (full directory for DK, curated for NO/SE/FI). This adds value beyond the schema. Slight deficiency: no mention of authentication or pagination, but acceptable for a simple listing tool.

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?

Four sentences, each serving a distinct purpose: purpose/scope, use cases, exclusions, and behavior/return info. Front-loaded, every sentence is necessary and adds value. No fluff.

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?

Given the tool's simplicity (2 optional parameters, no output schema) and 18 sibling tools, the description covers purpose, usage guidelines, alternatives, behavior variations by country, and return format. It is complete for an agent to decide when and how to use it.

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 coverage is 100%, so baseline 3. The description adds context about country-specific results and return format (names and dealer IDs), which enhances understanding of how parameters affect output. It doesn't elaborate on 'all' or 'query' beyond schema, but the real-world usage context compensates.

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 clearly states the tool lists grocery chains with dealer IDs for specific countries (DK/NO/SE/FI). It distinguishes itself from siblings by explicitly stating it is not for deals (use search_deals or deals_this_week) and specifying use cases for get_store_offers and update_household.

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 explicit 'USE WHEN' and 'NOT FOR' guidance, including alternative tool names (search_deals, deals_this_week). It also clarifies the country scope, giving the agent clear decision criteria.

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