parse_invoice_ae

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

With no annotations provided, the description carries the full burden and does so thoroughly. It discloses that the tool extracts EN 16931 fields plus AE extensions, re-validates as an AEInvoice, re-checks TRN format and tax-rate/category consistency, and returns a structured success/failure envelope.

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?

The description is well-structured and front-loaded: purpose, accepted input scope, behavioral detail, then return format. Each sentence adds distinct information with no filler or redundancy.

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?

For a single-parameter parse tool with an output schema and no annotations, the description is complete. It covers accepted document types, extracted fields, validation behavior, and the exact success/error response shape, leaving no operational gap for an agent choosing or calling the tool.

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% for the single xml_content parameter, so the baseline is 3. The description adds valuable semantic detail beyond the schema by specifying that billing and self-billing documents are accepted and that both Invoice and CreditNote roots are valid, which helps the agent understand what content to pass.

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 opening sentence states a specific verb and resource: parse a PINT AE UBL 2.1 XML invoice into a structured dict. The description further distinguishes this from sibling generate/validate tools by clarifying it extracts fields and re-validates parsed content, leaving no ambiguity about its role.

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 description gives clear context on acceptable inputs: PINT AE billing or self-billing UBL 2.1 documents with Invoice or CreditNote roots. It does not explicitly name alternatives or state when not to use the tool, but the accepted-input scope and parse-focused behavior make the usage context clear.

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