list_stores

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

No annotations are provided, so the description carries the burden of behavioral disclosure. It explains the core behavior (listing stores near ZIP with active ads and deal counts) and the optional ZIP behavior, but does not mention potential error conditions, pagination, or rate limits. This is adequate for a simple read-only tool but lacks richer behavioral context.

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?

The description is concise and well-structured: a clear one-sentence purpose statement, a 'Start here' usage hint, and a compact Args section. Every part earns its place without redundant detail or excessive length.

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 single-parameter tool with an output schema present, the description covers the essentials: what the tool does, the input format, and optional behavior. It does not explain return-value details, but the output schema fills that gap. Minor missing context includes what happens if no ZIP is provided and no default is configured, but this is a small omission for the tool's low complexity.

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 schema only provides a title and default for zip_code, with no description. The tool description fully compensates by specifying it as a 5-digit US ZIP code, giving an example, and clarifying it is optional when a server default exists. This adds significant semantic value beyond the schema, making the parameter's meaning and usage unambiguous.

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's function: 'List grocery stores near a ZIP code that have an active weekly ad, with how many deals each is running.' This is a specific verb+resource+scope and differentiates itself from siblings like search_deals or store_circular by focusing on store-level results with deal counts. The addition of 'Start here' further positions its role.

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?

'Start here' explicitly signals when this tool should be used as an entry point, giving clear context. However, it does not explicitly mention when not to use it or name alternative tools for other scenarios, so it stops short of full exclusionary guidance.

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