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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior. The description adds valuable context beyond those: data provenance (OpenStreetMap via Nominatim), no auth required, and ODbL licensing/attribution requirements. No contradiction with annotations.

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 sentences with front-loaded purpose, immediate examples, and no filler. Every clause earns its place: operation, input examples, output type, optional restriction, and legal/auth notes.

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 read-only geocoding tool with an output schema and annotations covering safety, the description is complete: it states the data source, license, auth requirements, optional country restriction, and expected output shape. Nothing an agent needs to invoke it correctly is missing.

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 100%, with all four parameters already described in the input schema. The description adds only illustrative query examples and a paraphrase of the country_codes restriction; it does not introduce new semantics for language, limit, or query formatting beyond what the schema provides.

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 states a specific verb ('Forward geocode') and resource (free-form address/place name → coordinates and structured address data), with concrete examples that make the operation unmistakable. It clearly distinguishes itself from reverse and lookup siblings by naming the forward direction and the data source (OpenStreetMap via Nominatim).

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 description makes the core use case clear: forward geocoding of free-form text. However, it does not explicitly name alternatives such as nominatim.geocode.reverse or nominatim.geocode.lookup, nor does it state when not to use this tool. Context is clear but exclusions are absent.

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