Get Invoice E-Invoice XML

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

Annotations already declare readOnly, idempotent, and non-destructive. Description adds that output is EN16931-compliant XML in auto-detected format, and that it's only available after save/send. No contradiction.

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?

Bilingual but each language is concise. Front-loaded with purpose and output format. Second sentence adds important precondition. No wasted words.

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?

Given one required parameter and existence of output schema, description covers the purpose, output type, and precondition. Could mention error conditions but sufficient for a simple retrieval 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% with only the 'id' parameter described. The description's mention of 'for an invoice' adds minimal extra meaning over the schema. 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?

Clearly states the tool downloads e-invoice XML for an invoice, specifies the formats (UBL, CII, etc.), and distinguishes from sibling tools like get_invoice_pdf and get_invoice by focusing on XML output.

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?

Provides explicit precondition that the invoice must be saved/sent. Does not list alternatives but the context is clear enough for agents to know when to use this tool versus similar ones like send_einvoice or validate_einvoice_xml.

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