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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is known. The description adds valuable behavioral context: the external data source (Open-Meteo / Nominatim), a per-call cost, and the GET HTTP method, which are not present in the annotations or schema.

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?

The description is a single compact sentence broken into scannable fragments: operation, mapping, source, pricing, and endpoint. It is front-loaded with the core purpose and contains no filler or redundant restating of the tool name.

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?

For a simple read-only geocoding tool, the description plus fully-covered schema is largely sufficient. It states the key outputs, the source, and the price, though it omits a detailed response structure (no output schema). Given the low parameter count and clear scope, the missing response shape is a minor gap.

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%, with q, count, and country each documented and exemplified (e.g., 'London', '3', 'GB'). The description itself does not elaborate on parameters, so it adds nothing beyond the schema, matching the baseline score of 3.

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?

The description opens with the specific operation 'Forward geocoding' and an explicit mapping 'Place name → coordinates, country, timezone,' which clearly distinguishes this tool from siblings like v1_reverse_geocode and v1_ip_geolocation. The resource (place name) and the output (coordinates) are concrete and immediately understandable.

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?

The term 'Forward geocoding' provides clear context for when to use it: when you have a place name and need coordinates or location metadata. It does not explicitly name alternatives or state when-not-to-use, but the directionality is self-explanatory and differentiates from the reverse geocoding sibling.

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