geocode

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

Description says 'search' (read-like), but annotations set destructiveHint=true, suggesting modification. This contradiction confuses agent behavior. Description adds no further 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?

Single sentence is concise and front-loaded, but lacks structure (e.g., no sections) and provides minimal detail for a 3-param tool.

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?

With contradictory annotations and no output schema, description misses essential return format info and fails to disclose behavioral implications, leaving the agent underinformed.

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 has 100% description coverage, but description adds geocoding context ('by name') beyond param details. This clarifies the tool's purpose and differentiates forward vs reverse geocoding.

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 verb 'search' and resource 'location by name' (geocoding), distinguishing it from sibling tools like calculate_route and find_nearest_stations.

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 implies geocoding use via 'search by name' but provides no explicit when-to-use vs alternatives, no exclusions, and no context-sensitive guidance.

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