find_nearest_store

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

Annotation contradiction: annotations specify readOnlyHint=false and destructiveHint=true, but description claims read-only unless select=true. This inconsistency undermines trust and does not disclose the actual destructive behavior.

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 with front-loaded purpose and a usage warning. Efficient with no wasted words, though could be slightly expanded for clarity.

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?

Incomplete for a tool with 4 undocumented parameters and potentially destructive side effects. Does not explain output or the effects of select=true, leaving gaps given the annotation hints.

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?

With schema description coverage at 0%, description only hints at the 'select' parameter's effect. No explanation of 'label' or the exact behavior when select=true is provided, leaving agent uninformed.

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?

Verb 'Find' and object 'delivery store for coordinates' clearly state purpose. Differentiates from sibling 'set_store' by focusing on location lookup rather than setting a preference.

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?

Provides guidance to not pass private addresses and mentions read-only condition unless select=true. However, does not explicitly state when to use alternatives like 'set_store' or 'search_products'.

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