search_regions

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

No annotations provided, so description carries full burden. It discloses hierarchical navigation, default code, and rate limit fallback. Does not detail error handling for invalid codes, but output schema exists and read-only nature is clear from 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?

Description is concise with bullet points and a clear example. Front-loaded with purpose. Minor redundancy (e.g., '지역 검색' repeated), but overall efficient.

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 single parameter and existence of an output schema, the description covers hierarchy, default, example, and fallback. Lacks details on error cases or edge conditions, but adequate for a fairly 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 0%, requiring description to compensate. It fully explains the parameter 'cortar_no' as a 10-digit region code with default for entire country, and demonstrates usage in the example. This adds significant meaning beyond the schema.

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?

Description clearly states the tool is for region search with hierarchical exploration (시도 → 시군구 → 읍면동). It provides specific verb 'search/explore' and resource 'regions hierarchy', distinguishing it from sibling tools like get_complexes or get_articles.

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?

Explains step-by-step usage with examples and default behavior. Missing explicit 'when not to use', but context from sibling tools and the description itself implies it's for region code navigation only. Mentions automatic fallback for rate limiting.

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