Validate Tax Compliance

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds useful scope context by naming the rule categories checked and disclosing that it also estimates deductible input VAT, but says nothing about batching behavior, failure modes, or performance 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 dense sentence with no filler, front-loaded on the core action and immediately qualified by the rule set. Every clause carries information.

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?

With annotations covering the safety profile and an output schema covering return values, the description only needs to convey what is checked and roughly what comes back, which it does. Minor gap: it does not indicate the scope of validation (per-transaction results, aggregate, or both).

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?

There is a single parameter (txn_ids) with 100% schema description coverage, so the schema already explains it. The description adds no format or scoping detail (e.g., max number of ids, mixed-vendor ids), so the baseline of 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 gives a concrete verb ('Check') and resource ('transactions') and enumerates the specific rule families it applies (receipts, clean-card merchants, entertainment evidence, late-night/weekend use), plus a second function (estimating deductible input VAT). This is far more specific than the name alone. It does not explicitly differentiate from the overlapping sibling find_missing_receipts, which is the only thing keeping it from a 5.

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?

Usage is implied rather than stated: an agent can infer this is the compliance/validation step, but there is no guidance on when to call it versus find_missing_receipts or list_card_transactions, and no stated prerequisites. The closest sibling (find_missing_receipts) overlaps on the 'receipts' dimension and is never mentioned.

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