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

With no annotations, the description carries the full burden and does well: it discloses accepted input standards (UBL 2.1, CIUS-RO), the source system, and a pricing model with a failure caveat ('Costs 1 credit; not billed on errors'). It does not cover auth requirements, size limits, or what errors look like beyond the billing note.

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, front-loaded with input then output then cost, with no filler. It is long due to legitimate enumeration of returned fields, but every clause carries information an agent would otherwise have to guess.

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?

No output schema exists, so the description correctly enumerates the returned structure (header fields, parties, payment means/IBAN, lines, VAT breakdown and totals). Combined with a fully documented input parameter and the cost caveat, an agent has everything needed to call and interpret this 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% and there is a single parameter whose schema description already states the UBL 2.1 / RO e-Factura / CIUS-RO constraint. The description largely restates that format in prose, adding little syntax or format detail beyond the schema, 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?

States a specific verb (turns/parses) on a specific resource (UBL 2.1 e-Factura invoice or credit note XML) and names the concrete output (clean English JSON). It is clearly distinguishable from siblings like validate_efactura, efactura_to_pdf, and generate_efactura without opening any 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?

It supplies the input context ('e.g. downloaded from ANAF SPV'), which implicitly tells the agent what kind of document fits, but there is no explicit when-to-use versus validate_efactura or efactura_to_pdf, nor any stated prerequisites or exclusions. Usage is implied rather than directed.

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