Delete Commitment Change Order Line Item

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

The description reinforces the destructive nature by stating 'This cannot be undone' and 'Permanently removes', adding context beyond the destructiveHint annotation. It also lists required parameters, though it could mention idempotency or side effects.

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 repetitive, stating the same idea three times ('Deletes', 'Use this to permanently delete', 'Permanently removes'). It could be condensed to a single sentence with the required parameters and warning.

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?

The description covers basic functionality and required parameters, but lacks context on preconditions (e.g., change order status), what happens if the item is already deleted (idempotency), and does not mention that this applies only to line items, not entire change orders.

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?

With 100% schema coverage, the description adds no new meaning to parameters beyond listing them. The schema already provides identifiers; the description does not clarify parameter roles further.

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 deletes a specified commitment change order line item, specifying the exact resource and action. It distinguishes from sibling delete tools by naming the specific resource type.

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?

The description indicates to use this for permanent deletion of line items, but does not provide explicit scenarios when not to use it or suggest alternatives. It lacks guidance on prerequisites or conditions.

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