find_stores

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

No annotations, so description carries full burden. Discloses input types (Swiss ZIP, GPS, free-text address), geocoding via Nominatim for address, and output fields (name, address, hours where available). No contradictions.

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 sentences plus a usage tip. Some overlap with input schema but efficient and informative. Could be slightly tighter but no major waste.

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 no output schema and 3 params, description covers input and output sufficiently (store details, hours). Lacks details on pagination or error handling, but acceptable for a store-location tool.

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 100% already documents parameters well. Description adds context: notes speed preference for zip/lat-lng over address, chains can be omitted, and explains each input variant.

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?

Description clearly states it finds grocery stores near a location with filters (chain, radius). Provides example use cases and distinguish from siblings like find_stock.

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?

Description gives concrete usage examples ('find a Migros near me', 'which Coop branches are in 8001?') and implies when to use (store location) vs. stock check. Lacks explicit when-not-to-use but context is sufficient.

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