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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is known, but the description adds nothing further — no note on lookup semantics, batching behavior, or what happens with invalid OSM ids. With annotations carrying the burden, the description contributes no extra behavioral context.

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 single four-word fragment is not concise so much as under-specified — it is a title repeated as a sentence, with no front-loaded actionable content for the agent to act on.

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 5-parameter tool sitting alongside two geocoding siblings, the description omits the one thing only it can supply: which geocoding operation this is and when to pick it. The output schema and full parameter coverage help, but sibling disambiguation is missing entirely.

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 each of the five parameters (including the required osm_ids prefix format N/W/R) is documented in the schema. The description adds no meaning beyond it, so the baseline of 3 applies when the schema does the heavy lifting.

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?

"Geocoding place lookup" essentially restates the tool name (geocoding_lookup) without adding a specific verb+resource distinction. It does not differentiate the tool from its siblings geocoding_reverse or geocoding_search, leaving the agent to infer which geocoding variant applies.

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 when-to-use guidance, no prerequisite information, and no mention of the alternatives geocoding_reverse (coordinate-to-place) or geocoding_search (name-to-place). The agent must open the schema and compare siblings manually to decide.

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