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

The annotations already declare readOnlyHint=true and openWorldHint=true, which cover the safety profile. The description adds useful behavioral context: the card data is automatically recognized, the operation requires a lawful processing basis, and each call consumes 60 points. It does not disclose whether the file is stored or what happens on failure, but this is acceptable given the read-only annotation.

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-loaded with the main action, then adds the input requirement, legal condition, and cost in short sentences. The bilingual phrasing repeats some content, but the Korean sentence adds the detail that the card's written information is automatically recognized, so the redundancy is mild and purposeful.

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 one-parameter tool, the description covers what input to provide and when use is lawful. With no output schema present, it would benefit from stating the response format (e.g., whether it returns true/false or a result object). The absence of a sibling differentiation also leaves a small contextual gap, but the core call is understandable.

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?

The input schema already fully documents image_url as a downloadable https URL with allowed formats (jpeg/png/pdf) and a 50MB limit, so the baseline is 3. The description reinforces 'image or PDF' and 'one file' but adds no new technical details about the URL parameter beyond the schema.

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 opens with a specific verb and object: 'Verify the authenticity of a Korean resident registration card from an image or PDF file.' It clearly scopes the tool to image/PDF input and explicitly says no text input is needed. However, it does not differentiate itself from the nearly identical sibling names identi_card_image2 through identi_card_image5.

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 a clear precondition for use ('정보주체의 동의 등 적법한 처리 근거를 확보한 경우에만 사용하십시오') and states that only a single file is required. It does not, however, mention when to prefer this tool over alternatives such as identi_card1 or the OCR variants, leaving the choice to inference.

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