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

Annotations already establish readOnlyHint=true, idempotentHint=true, and openWorldHint=true. The description adds useful behavioral context beyond those hints: it states that validation is deterministic, includes checksum validation, and has explicit scope per identifier. It does not detail rate limits or authentication needs, but the annotations reduce the burden.

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: it starts with the 'one call, one receipt' value proposition, lists the covered identifiers, and then states the validation behavior. There is no redundant or wasted wording.

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?

The tool has an output schema and annotations that cover safety and idempotency, so the description does not need to explain return values or read-only behavior. It adequately conveys the combined verification purpose and validation model, though it could clarify whether any combination of the optional identifiers is acceptable and when the pack should be preferred over single-identifier checks.

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 all three optional parameters. The description reinforces the identifiers and specifies 'settlement IBAN' for a Chinese counterparty, but it does not add format details, checksum scope, or combination rules beyond what the schema and example already provide. Baseline 3 is appropriate when the schema carries the parameter semantics.

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 clearly states that this is a combined verification pack for Chinese counterparties covering USCC, settlement IBAN, and SWIFT/BIC, with deterministic structure and checksum validation. It implies differentiation from individual identifier checks through 'one call, one receipt,' though it does not explicitly name siblings like uscc_check or iban_check.

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 'for a Chinese counterparty' and 'one call, one receipt' implies using this tool when multiple Chinese supplier identifiers need to be checked together. However, there is no explicit guidance on when to choose this combined pack versus the individual sibling tools such as uscc_check, iban_check, or swift_bic_check.

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