get_region_code

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

Without annotations, the description discloses the multiple-match behavior and return fields, though it omits potential error handling or auth requirements. Still, it provides good transparency for a simple conversion tool.

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 well-structured with Args and Returns sections, concise yet complete, with no wasted words.

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?

Given the tool's simplicity (one parameter, output schema), the description fully covers purpose, usage, input format, handling of multiple matches, and return values.

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?

The schema parameter 'query' has no description (0% coverage), but the tool description compensates fully by explaining it accepts free-form text and providing examples like '마포구', '서울 마포구'.

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 clearly states the tool converts user-supplied region names to a 5-digit legal district code for the MOLIT API, which is distinct from sibling tools that handle calculations, trades, or rents.

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 explicitly states 'Must be called before any trade or rent tool' and provides guidance on handling multiple matches by showing the matches array and confirming with the user.

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