Practical Korea guide

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

No annotations are provided, so the description carries the full burden. It discloses that the output is 'short, practical guides' (implying static reference content, not live/mutating data), which is useful, but it says nothing about language, format, or personalization.

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 zero filler; the purpose is front-loaded and the topic enumeration follows immediately. Every element earns its place.

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 simple one-enum-parameter lookup tool with no output schema and no annotations, the description is nearly sufficient: it tells the agent what comes back and what topics exist. Minor gaps remain around output format and language, but nothing critical for correct invocation 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 description coverage is 0%, but the single parameter is an enum whose values the description simply restates ('airport, apps, emergency, transit-card'). The enum values are largely self-descriptive, so the description adds little semantic depth beyond the schema's own enum list.

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?

States a specific resource (short, practical guides for visitors and foreign residents in Korea) with a clear verb-implied action of retrieving them. The topic list further scopes the content. It does not explicitly contrast itself with siblings like subway_route or korea_holidays, but the topic framing makes its domain distinct.

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?

Usage is implied by 'for visitors and foreign residents' and the topic list, but there is no explicit when-to-use, when-not, or routing to siblings such as subway_route for transit directions or korea_holidays for holidays. An agent can infer the context but must decide on its own.

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