Send E-Invoice

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

Discloses async behavior and the need to poll for status. Annotations indicate non-readOnly, but description adds context on immediate return of workflowRunId and honest 'unavailable' response if backend missing.

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-loaded with core action, then lists formats and modes. Spanish translation adds length but is helpful. Could be slightly more concise, but overall well-structured.

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?

Covers all critical aspects: purpose, async behavior, format/mode selection, backend availability, and reference to status tool. Output schema exists, so return value explanation is unnecessary.

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%, but description adds significant value by mapping each format to specific country/channel use cases and explaining each dispatch mode, going beyond enum names.

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?

Description clearly states the tool dispatches an e-invoice via a selected transport channel. It lists supported formats and dispatch modes, distinguishing it from siblings like 'validate_einvoice_xml' and 'send_invoice'.

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 guidance: use this to dispatch e-invoices, poll 'get_einvoice_status' for completion, and choose format based on country/channel. Mentions backend unavailability scenario.

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