generate_cii_invoice

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

No annotations provided, so description bears full burden. It lists accepted fields policy, return formats for success/validation error/unexpected error, and mentions profile URN specifics. No contradictions.

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?

Description is concise and well-structured, with clear separation of purpose, usage, and return values. Slightly verbose but no unnecessary fluff.

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 output schema exists, return values are described in text. Parameter is well covered. Distinguishes from many siblings. Provides complete guidance for agent invocation.

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 invoice_data, but description adds useful context about field requirements and profile URN for Factur-X/ZUGFeRD, going beyond schema details.

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 description clearly states it generates a CII XML document from an ItalianInvoice dict, specifies the format (CII-D16B), and distinguishes from siblings like generate_fattura_xml for FatturaPA XML.

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?

Explicitly says when to use (for CII wire format, Factur-X, ZUGFeRD) and when not to use (not for FatturaPA), and mentions alternatives like generate_fattura_xml() and generate_ubl_invoice().

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