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

Annotations already declare readOnlyHint=true and openWorldHint=true. The description adds value beyond these: the legal/consent processing requirement and the cost note ('[호출당 60포인트]'). It does not contradict annotations — verification is a read-only operation consistent with readOnlyHint. It stops short of richer disclosure (e.g., what the verification response contains), but adds meaningful 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?

The description is compact and front-loads the primary purpose, followed by usage guidance, legal note, and cost. It is mildly redundant — the English lead sentence and the Korean sentence express essentially the same purpose — but remains reasonably tight with no extraneous filler. Each sentence contributes, though two could be merged.

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 single-parameter tool with 100% schema coverage and read-only annotations, the description is largely adequate. The main gap is the absence of any statement about the verification output format (boolean result, OCR'd fields, report) since no output schema exists. Given the sibling cluster and the sensitive personal-data nature, slightly more on expected behavior would strengthen it.

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 schema already documents image_url (downloadable https URL, allowed formats jpeg/png/pdf, 50MB limit). The description marginally supplements this by stressing single-file, no-text input, but does not add format or syntax details beyond what the schema provides. Baseline 3 is appropriate when the schema carries the parameter documentation.

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 states a specific verb and resource: 'Verify the authenticity of a Korean resident registration card from an image or PDF file.' The title adds '[Image/PDF]' which distinguishes it from the text-input siblings (identi_card1-5). However, it provides no differentiation among the nearly identical image siblings (identi_card_image1-5), so it doesn't fully separate it from the closest alternatives.

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 description gives clear context that this tool is for file-based input ('텍스트 입력 없이 파일 하나만 전달하면 됩니다' — pass a single file, no text input) and adds a legal prerequisite (consent of the data subject must be secured). It implies file-vs-text selection but does not explicitly name alternatives, and gives zero guidance on selecting among the five identical image endpoints, which is the agent's real selection problem.

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