invoice_convert

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

Discloses that profile downgrades may cause data loss and requires allow_data_loss=True. Without annotations, the description carries full burden but omits other behaviors like idempotency, side effects, 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?

Three concise sentences that efficiently convey purpose, supported operations, and a key warning. No redundant 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 main conversion capabilities and data loss warning. However, lacks description of output format (no output schema) and input constraints (e.g., requirement for valid invoice). Could be more complete for a complex conversion 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?

Explains target_profile, target_syntax, and allow_data_loss partially via context. But xml_content and xml_base64 are not described (e.g., format requirements). Schema coverage is 0%, so the description should compensate more thoroughly.

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 verb 'Convert' and specifies the invoice types (ZUGFeRD, XRechnung) and supported operations (profile upgrades/downgrades, syntax conversion). Distinguishes from sibling tools like invoice_create or invoice_validate by focusing on conversion.

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 clear context on when to use (conversion between profiles/syntaxes) and warns about data loss for downgrades. However, does not explicitly mention when not to use or suggest alternatives among siblings.

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