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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered by structured data. The description adds the meaningful input-domain constraint that only Korean addresses/places are supported, but says nothing about lookup latency, failure behavior for unresolved queries, or result format. It contributes some context beyond annotations, appropriate for a 3.

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?

Very compact and front-loaded, stating the core transformation first and the consumer second. The Korean and English sentences are semantically redundant, which serves a bilingual audience but slightly duplicates content rather than extending it. Still efficient overall.

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 single-parameter, read-only lookup tool with a fully documented schema and safety annotations, the description covers purpose, input domain, and downstream use. The only minor gap is that with no output schema, the description does not indicate the shape of the returned coordinates, but that is a small omission for such a simple tool.

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% for the single 'query' parameter, and the schema already supplies the examples (강남역, 세종대로 110). The description does not add syntax, format, or disambiguation guidance beyond the schema, so the baseline 3 for high coverage 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?

The description states a specific verb+resource pair: it converts Korean addresses or place names into latitude/longitude. It also names the downstream consumer (area_stats), so an agent instantly understands the tool's role and cannot confuse it with any sibling. Nothing here restates the tool name as a tautology.

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 parenthetical '(coordinates to use in area_stats)' gives explicit context for when this tool is needed, effectively routing the agent from area_stats to geocode. There are no exclusions or when-not-to-use conditions stated, but with no competing geocoder sibling, little more is required. Clear context without exclusions lands this at 4.

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