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

No annotations are provided, so the description carries the burden of revealing behavior. It discloses the core output shape: a single pass/review/fail verdict with confidence and flags, which is genuinely useful. It does not address side effects, rate limits, or partial-parameter behavior, but for a screening tool this is adequate disclosure.

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 compact sentences that front-load the high-signal information: what the tool is, what it fuses, and when to call it. Every sentence earns its place and there is no redundant 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 definition includes the overall output format and typical business triggers, which is good for a composite-feature tool. However, with five optional parameters and no output schema, it does not explain minimum required inputs or how partial data affects the verdict, leaving an agent uncertain about how to construct valid calls.

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% and each parameter already has a short descriptor such as '20-char LEI code' or 'VAT number without country prefix'. The description maps the checks to complementary vocabulary (VIES, GLEIF, checksum) but does not explain required combinations or how many parameters must be supplied for a meaningful verdict.

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 defines a composite KYB/counterparty due-diligence tool and enumerates the five checks it runs. It distinguishes itself from sibling single-purpose validators such as eu_vat_validate, lei_lookup, iban_validate, and sanctions_screen by explicitly saying 'ONE call' and describing a fused verdict.

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?

It gives concrete, high-value call signals: before onboarding a customer, paying a supplier, or transacting with an EU business. It does not explicitly tell the agent when to use a sibling single-source tool instead, so it lacks an explicit exclusion or alternative rule.

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