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

Annotations only declare readOnlyHint=true, so the description earns credit for disclosing output shape: surname convention mapping, hyphenated given name, and both Western and Korean order. It stays silent on ambiguity (e.g., which romanization variant for an ambiguous syllable) and on behaviour for non-Hangul input.

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?

One dense, front-loaded sentence that leads with the action and immediately constrains the domain. The trailing 'Free.' fragment adds no selection value and the sentence is somewhat overloaded with examples, keeping it just below top marks.

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 describing the return value, and it does so adequately via the surname-mapping and ordering conventions. Handling of edge cases such as invalid or non-Hangul input is not covered.

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 coverage is 100% for the single 'name' parameter, so baseline is 3. The description adds genuine meaning by specifying Hangul input, illustrating multi-syllable surname handling (남궁), and clarifying that both name orders are produced.

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 verb is specific ('Romanize') and the resource is narrowly scoped to 'a Korean personal name (Hangul)', which separates it from address and product-title siblings. It stops short of naming the neighbouring romanize_korean tool, so the boundary with that sibling is left to inference.

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 phrase 'the way it usually appears in passports/English docs' implies the intended context, but there is no explicit when-to-use statement and no alternative named. With a directly overlapping sibling (romanize_korean) present, the missing routing guidance is a real gap.

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