osm_geocode

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

With no annotations, description fully discloses payment requirement, pricing, fallback behavior (402 accept-list), and output structure. 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?

Three concise sentences covering purpose, pricing, and authorization mechanism. No extraneous information.

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?

Covers key aspects: input, output, payment flow. Lacks mention of error handling or rate limits, but sufficient for typical invocation.

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 covers both parameters with descriptions; description adds important context on '_payment' (x402 v2 authorization, effect on response) beyond schema.

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?

Clear specific verb ('forward geocode') and resource ('OpenStreetMap Nominatim'), with explicit output (lat/lon, normalized address block, match_quality). Differentiates from sibling 'osm_reverse_geocode' by direction.

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?

Explains how to invoke with optional payment parameter and consequences of omitting it. Lacks explicit comparison to alternatives but provides sufficient context for use.

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