invoice_create

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

Discloses key behaviors: supports multiple profiles, XML output rejection without opt-in, and regulatory mandate. However, no annotations exist, and it omits details like return format or error handling.

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?

Single paragraph efficiently conveys core function, profile support, and regulatory context without redundancy. Every sentence adds value.

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 main features and constraints, but lacks description of return values or output format details. Given complexity (5 params, no output schema), it is mostly adequate but could be more thorough.

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?

Adds meaning beyond the schema for output_format (rejection of non-XML) and transitional_period_opt_in (explanation of opt-in). Schema coverage is low (20%), so description compensates, but pretty_print and invoice object remain vague.

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 the tool generates ZUGFeRD or XRechnung invoices in XML format, lists supported profiles, and distinguishes from siblings (invoice_convert, invoice_parse, etc.) by focusing on creation.

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 specific conditions for when to use (e.g., German VAT buyer requires EN 16931) and opt-in rules, but does not explicitly compare to sibling tools like invoice_validate or invoice_convert.

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