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

The annotations already cover read-only, idempotent and non-destructive behavior; the description adds context the annotations do not carry, namely that one call counts as one geocoding request (quota cost) and what the result payload contains (name, address, lat/lon, bounding box, osm element, overpass_area_id). It does not describe error or empty-result behavior, so it stays at 4.

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?

It is front-loaded with the core purpose and stays to a few dense sentences with no filler. The enumeration of returned fields is slightly list-like but each item is functional information, so it earns its place.

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 no output schema, the description usefully enumerates return fields, and it explains how to chain results into overpass_query. For a seven-parameter tool with nested objects and an 86% schema coverage, the schema handles the rest. The only gap is the absence of any note on empty or ambiguous results.

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 coverage is 86%, so the schema already documents most parameters. The description restates the supported languages (en, de, fr), which duplicates the enum already in the schema, and adds no meaning for near, within, kind, limit or country_codes. Baseline 3 is appropriate when the schema carries the load.

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 a specific verb and resource: 'Finds places, addresses and points of interest by name (geocoding)', and adds that partial text works for autocomplete. The phrase 'by name' implicitly contrasts with reverse_geocode, but no sibling is named explicitly, so the differentiation falls slightly short of a 5.

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?

There is no explicit when-to-use or when-not guidance, and no comparison to reverse_geocode or overpass_query. It does, however, give actionable follow-up guidance: results carry an osm element, and for ways and relations an overpass_area_id usable in overpass_query as area(id:N). That is real workflow guidance, even if selection guidance between siblings is left implied.

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