Delete Line Item

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

With no annotations, the description carries the full behavioral burden and discloses almost none of it: it does not say the deletion is irreversible, whether it requires specific permissions, what happens if the line item belongs to a non-draft invoice, or what the response looks like. The draft-invoice scope is the only behavioral constraint offered.

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?

A single front-loaded sentence with no filler; the scope constraint appears immediately after the action. It is efficient, though arguably too terse for a destructive operation with no annotations.

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?

For a destructive mutation with no annotations and no output schema, the description should at minimum signal irreversibility and permission requirements. The draft-invoice constraint helps, but the safety and error semantics an agent needs before calling this are absent.

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 description coverage is 100% for the single id parameter, so the schema already fully documents it. The description adds no syntax, format, or ID-source detail beyond what the schema provides, so the baseline of 3 applies.

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?

States a specific verb (Delete) and resource (line item) and adds a scoping qualifier (from a draft invoice), which separates it from productive_create_line_item and productive_update_line_item. It stops short of naming those siblings explicitly, so it is clear but not fully differentiated.

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?

'From a draft invoice' implies the precondition that only draft-invoice line items are deletable, which is useful routing context. However, it never says when to delete versus update, and gives no guidance for non-draft invoices or what to do instead.

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