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

Annotations already cover the safety profile (readOnlyHint=false, destructiveHint=false, openWorldHint=true, idempotentHint=false). The description adds genuinely useful context beyond them: no data is transmitted externally, and credit consumption may apply. It could go further (e.g. what 'readOnlyHint=false' concretely means here), but it earns credit for the added behavioral detail.

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 purpose in the first sentence and follows with three short, useful statements. Efficient overall, though the raw POST endpoint adds little value for an agent choosing a tool.

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 carries the burden of describing the return value; it names the Universal Invoice JSON structure and its main sections, which is reasonably sufficient. Parameter semantics are fully covered by the schema, so coverage is adequate.

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 all five parameters (xml, data_base64, validate, einvoice_type, include_unmapped_fields) are already fully documented in the schema. The description adds no syntax or format guidance beyond that, so baseline 3 is correct.

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 (Convert) and resource (an e-invoice in XML or hybrid PDF) plus the target format (Universal Invoice JSON, with parties/lines/taxes/totals). This clearly distinguishes it from siblings like dochorizon_validate_einvoice and dochorizon_capture_einvoice.

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 only implied: the standard path is to feed an existing e-invoice XML/PDF and get JSON back. It never states when to prefer this over validate_einvoice or capture_einvoice, nor any prerequisites (e.g. credit requirements, auth). Adequate but leaves the agent to infer.

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