save_invoice_desc

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

Annotations already indicate destructiveHint=true, so the description's mention of 'save' is consistent. The description adds value by explaining drg_amount behavior (VAT codes), but lacks details on update vs. create (though the schema's 'id' field hints at this), idempotency, or error scenarios.

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?

The description is very concise at one sentence plus a critical note. Every part is useful, though the non-English parenthetical may be unnecessary. It is front-loaded with the core action.

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 the tool's complexity (9 params, no output schema, destructive nature), the description covers the main purpose and the key drg_amount nuance but omits return value, prerequisites, and relationship to other save tools. The schema descriptions fill some gaps, but more context would help an agent invoke it correctly.

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% with descriptions for all 9 parameters. The description additionally clarifies drg_amount's special values (0 for zero-rate, -1 for non-taxable), which adds meaningful context beyond the schema.

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 action ('Save') and the resource ('goods/service line item on an invoice'). It distinguishes from sibling tools like delete_invoice_desc and get_invoice_desc. The special drg_amount values add specificity.

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?

No guidance is provided on when to use this tool versus alternatives like save_invoice or save_invoice_a. The description does not mention prerequisites (e.g., invoice must exist) or when not to use it.

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