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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds the behavioral detail that it checks a match against the registration number and returns 'match result plus current status.' However, it does not elaborate on edge cases, data-source behavior, or status semantics, and with an output schema present the return-value mention adds limited extra value.

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 three short sentences: purpose, use case, and return summary. Every sentence contributes distinct information, and the core verification behavior is front-loaded. There is no redundant or filler content.

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-record verification tool with full schema coverage, read-only/idempotent annotations, and an output schema, the description is largely complete. It states what is verified, when to use it, and what kind of result to expect. The only notable gap is lack of explicit differentiation from sibling tools, but that does not prevent correct invocation.

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 reinforces that representative_name and opening_date are used as match criteria, but it does not add meaning beyond the schema for business_number, address, or format details. The schema already documents formats and the optional address mapping.

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 and resource: 'Verify that a Korean business registration number matches the provided representative name and opening date.' This clearly states the tool's core function. It does not explicitly distinguish itself from siblings like check_korean_business_status, but the 'match' framing and single-record verification make the purpose reasonably clear.

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 usage context: 'Use for KYB / due-diligence before transacting with a Korean company.' This tells an agent when the tool is appropriate. It does not explicitly contrast with batch or status-only siblings, so exclusions and when-not-to-use guidance are missing, but the stated context is sufficient for most selection decisions.

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