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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so the safety and repeatability profile is covered. The description adds real value with 'deterministic structural checks', clarifying these are format/checksum validations rather than authoritative registry lookups — an important distinction. However, it never says what happens when all three optional fields are omitted or what a partial check reports.

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?

Two short sentences with the bundled scope front-loaded and zero wasted prose. The 'one call, one receipt' phrasing is slightly slogan-like but it does communicate consolidation efficiently.

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?

Output schema and annotations are present, so the description needn't explain return values. The remaining gap is behavioral: with zero required parameters, an agent has no signal about whether an empty call is valid or how a one-field invocation behaves. For a multi-check pack that gap matters.

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 coverage is 100% and each property already documents itself as optional, so the schema does the heavy lifting. The description lists the same three fields but adds no format hints, no indication of whether at least one is required, and no meaning beyond what the schema provides. Baseline 3 applies.

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 names a specific resource and scope: a bundled verification covering KRA PIN, IBAN and SWIFT/BIC. An agent can tell this is the consolidated East-Africa pack rather than a single-field check. It stops short of naming the siblings it replaces (kra_pin_check, iban_check, swift_bic_check), so differentiation is implied rather than explicit.

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?

'One call, one receipt' hints that this is the consolidated option, and 'East African trade corridors' implies the regional context. But there is no statement of when to prefer this over the individual kra_pin_check / iban_check / swift_bic_check tools, and no guidance on partial inputs. Usage is inferable, not specified.

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