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

Goes well beyond readOnly/destructive annotations: discloses the paid model ($0.01 USDC via x402, eip155:8453, payment in request _meta), states that an unpaid call returns payment requirements instead of a report, and clarifies only real invoices are charged. It also describes report contents (rule violations, plain-English fixes, UBL paths, correct amount values) and the 'autofix' signal for repair.

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?

Front-loads the trigger condition and free-tier alternative, and every sentence carries practical information. It is somewhat dense and run-on in the middle (report contents and payment terms packed together), but nothing is truly wasted.

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 no output schema, the description does the necessary work of explaining the report's contents and the payment-failure return, which is enough to call the tool correctly. The exact report structure (beyond the 'autofix' key) is only sketched, leaving a minor gap for a validation tool whose whole output is the report.

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%, so the xml and profile parameters are already fully documented, including the 'auto' CustomizationID behavior. The description adds no parameter-level detail beyond the schema, so the 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?

Names the specific action (validate a UBL e-Factura/Peppol invoice) and the downstream use case (before upload to ANAF SPV or Peppol send). It explicitly distinguishes itself from the sibling validate_invoice_free by quota and by being the paid tier, so an agent can choose without opening either schema.

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?

Gives explicit when-to-use: after the free quota of validate_invoice_free is exhausted, before uploading to ANAF SPV or sending via Peppol. It also routes follow-up work to fix_invoice when the report contains 'autofix', naming the alternative and the condition that selects it.

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