invoice_create

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

No annotations; description carries burden. It discloses supported profiles and planned PDF feature but omits side effects, error behavior, or output format specifics. Adequate but not exhaustive.

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?

Two sentences, front-loaded main purpose, no unnecessary words. Efficiently conveys key information.

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 standards, profiles, future roadmap. Missing details: return format, error handling, and explicit sibling differentiation. Reasonably complete for a focused generator 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 low (25%), and the description adds context about profiles and syntax choice (e.g., 'set profile to XRECHNUNG'). However, it does not fully compensate for undocumented parameters like pretty_print or output_format beyond their enum values.

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 ZUGFeRD or XRechnung invoices in XML formats, listing supported profiles. It implicitly distinguishes from siblings like invoice_convert or invoice_parse by the verb 'generate'.

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 guidance for XRechnung (profile and syntax choice) and mentions future PDF support. However, it does not explicitly contrast with siblings or state when not to use this tool.

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