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

Annotations already declare readOnly, idempotent, non-destructive, and open-world behavior. The description adds two useful facts beyond them: the upstream service is OpenStreetMap Nominatim and results are capped at 5. It says nothing about Nominatim's rate limits, result ranking/ambiguity, or behavior on no-match, which are the real behavioral risks for this tool.

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 short sentences, zero filler, and the core operation plus provider is front-loaded before the return details. Nothing could be removed without losing 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?

A one-parameter read-only tool with rich annotations and an output schema; the description covers what it does, who provides the data, and how many results come back. Missing only minor operational context such as rate limiting and what happens when the query matches nothing.

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 description coverage is 100% and there is a single required parameter already documented as 'Address or place name to geocode'. The description's phrase 'address or place name' restates the schema rather than adding format guidance (e.g. how specific or how ambiguous a query can be), so the baseline of 3 applies.

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?

States a specific verb (convert) and resource (address or place name to coordinates), plus the upstream provider, so the operation is unambiguous. The forward-geocoding direction implicitly contrasts with geo_reverse_geocode, but that sibling is never named, so the differentiation is left to inference.

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?

Usage is implied by the direction of conversion (address → coordinates), and the examples in the schema reinforce it. There is no explicit statement of when to prefer geo_reverse_geocode or geo_get_country, and no prerequisites or failure conditions are given.

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