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 covered. The description adds genuinely useful behavioral context beyond that: this is a paid call at $0.005 USDC per invocation settled via x402 on Base, which an agent must know before calling. It stops short of describing latency, rate limits, or failure modes.

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?

Purpose is front-loaded in the first clause and the payment model is a short, distinct trailing sentence. The middle enumeration of romanization systems is long but each named variant adds real disambiguation value, so it earns its space despite the density.

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?

There is no output schema, so the description carries the burden of explaining returns. It hints at a candidate list for the reverse direction but never says what the forward romanization call returns (single string vs. all variants), and it omits the 'kind' parameter's effect. Adequate but with clear gaps for a two-parameter, no-output-schema 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% for both parameters. The description partially compensates by implying the 'name' input may be either Hangul or romanized text, but it never explains the 'kind' enum (person vs company) or how it affects output, leaving one of two parameters undocumented in both schema and description.

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 names a specific verb (romanise/map back) and resource (Korean names), and enumerates the concrete output systems: Revised Romanization, McCune-Reischauer, Yale, North Korean forms, passport spellings. It is bidirectional (Hangul→roman and roman→Hangul candidates), which clearly separates it from siblings like kr_name_sanctions_screen or kr_entity_resolve.

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 the two directions described ('or map a romanised name back to Hangul candidates'), so an agent can infer the input shape. However, there is no explicit when-to-use guidance, no exclusions, and no routing to or away from related siblings such as kr_name_sanctions_screen or kr_entity_resolve.

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