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

With no annotations, the description carries the full burden and does deliver real behavioral facts: zero-retention data handling and a signed Ed25519 verifiable credential as proof of redaction. It omits the commercial mechanics entirely - that the call is metered at 0.008 EUR and gated by max_accepted_fee_eur, what happens when the fee ceiling is too low, whether redaction is reversible, and what the response body contains.

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 dense sentence with no waste, and the core operation is front-loaded. However it is jargon-saturated ('gate', 'VC', 'HRB') and packs four distinct concerns - retention policy, entity coverage, output credential, and commercial model - into one clause without structure.

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 and no annotations, yet the description never explains the return value (what the signed VC looks like, whether redacted text is returned or only a proof), and one of three parameters is undocumented everywhere. For a paid, credential-emitting compliance tool this leaves too much for the agent to guess.

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 67%, below the high-coverage threshold, and the description adds no meaning to any parameter. In particular ap2_intent_mandate_id is undocumented in both schema and description, and the relationship between max_accepted_fee_eur and the stated 0.008 EUR price is only visible in the schema, not explained behaviorally.

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?

States a specific verb+resource ('GDPR PII redaction gate') and enumerates the entity classes handled (IBAN, Tax-ID, HRB, Names) plus the emitted artifact (signed Ed25519 VC). It never names or distinguishes itself from the siblings screen_sanctions_and_kyb and validate_en16931_e_invoice, so an agent must infer the boundary itself.

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 word 'gate' hints that this is a pre-processing step before text leaves the agent, but there is no explicit when-to-use, no when-not-to-use, and no mention of the sibling tools as alternatives for sanctions screening or invoice validation. Nothing tells the agent how this fits into a compliance pipeline sequence.

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