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

No annotations are provided, so the description carries the full behavioral burden. It signals that the call yields an 'XDR1Receipt', hinting at a verification result artifact, but says nothing about whether the operation is read-only, whether it hits an external authority or performs local checksum validation, error behavior for malformed IDs, or rate limits.

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?

A single, front-loaded line with no filler, which is appropriate for a compact signature-style entry. The terseness is the right instinct, though the ad-hoc notation ('!', '?', '->XDR1Receipt') trades readability for brevity.

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?

There is no output schema, no annotations, and 0% schema description coverage, so the description is the only documentation an agent gets — and it is insufficient. It leaves the meaning of 'cc', per-kind ID formatting, and the nature of the returned receipt entirely unexplained.

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?

With 0% schema description coverage, the description supplies real value by listing the 13 accepted 'kind' values (iban, lei, vat, gstin, ein, abn, duns, bic, isin, npi, uk_crn, eu_eori, other) and by marking required ('!') versus optional ('?') parameters. However, 'id' and 'cc' get only type annotations: it never explains that 'cc' is a country code, which kinds require it, or how the expected ID format varies by kind.

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 entry is essentially the tool name expanded into a pseudo-signature ('verify_id=verify_identifier(...)'), which states a verb and a resource but adds little operational meaning about what verification actually entails. The kind enumeration shows the resource domain (IBAN, LEI, VAT, etc.), which helps, but the description never distinguishes this from siblings like screen_entity or solvency_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?

There is no when-to-use guidance, no prerequisites, and no routing toward or away from the sibling tools (reconcile, screen_entity, solvency_check). The agent is left to infer from the name alone that this applies to formatted business/financial identifiers rather than entity names or solvency checks.

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