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

Annotations already declare readOnlyHint=true, but the description adds significant context beyond that: it mandates legal consent/processing grounds and notes a per-call point cost. It does not describe the response format or error behavior, but the added legal and cost information goes beyond annotation coverage.

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 front-loaded and compact, but the English and Korean opening sentences are redundant restatements of the same idea. The detailed field enumeration also duplicates schema information. Some trimming would make it more concise and 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?

No output schema is provided, so the description should explain what the verification response contains (e.g., a boolean or detailed result), but it only says '진위 여부를 확인합니다' without clarifying the return structure. Input requirements are well covered, but the missing output semantics make the description incomplete for an agent to interpret results correctly.

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 100%, so the baseline is 3. The description groups required fields (birth_y/m/d, name, licen_no0-3) and optional fields (ghost_num, rrn1, rrn2) and explains the license number sections, but this largely mirrors the schema's own descriptions. It adds little new semantic meaning beyond what the structured schema already provides.

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 uses a specific verb 'verify' and explicitly names the resource: 'authenticity of a Korean driver license using text input.' This distinguishes it from image-based sibling tools like identity_document_driver_license and identi_card_image* tools by emphasizing textual input.

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?

Clear context is provided: this tool is for text-based verification of Korean driver licenses, and it requires a legal processing basis such as consent. It does not explicitly exclude other tools or name alternatives, but the text-input scope and legal requirement sufficiently clarify when to use it.

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