Delete Prime Change Order Line Item

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

Annotations already indicate destructiveHint=true, so the description's repetition of 'This cannot be undone' adds little new information. It provides the endpoint and required params, but does not describe response behavior or side effects beyond irreversibility.

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 verbose with redundant phrases like 'This cannot be undone' and 'Permanently removes the specified Prime Contracts' repeated. It could be condensed to a single clear sentence. The incorrect reference to 'Prime Contracts' also detracts from conciseness.

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 no output schema, the description does not cover return values or error scenarios. It mentions irreversibility and required params but lacks details on prerequisites, permissions, or post-deletion effects. Adequate but not comprehensive.

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 clear parameter descriptions. The description merely lists required parameter names without adding new semantic value, so it meets the baseline.

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 that the tool deletes a prime change order line item, but it incorrectly mentions 'Prime Contracts' multiple times instead of 'Prime Change Order Line Items', which causes minor confusion. The verb+resource is specific, and the endpoint clarifies the scope.

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 on when to use this tool versus sibling tools like delete_prime_change_order or delete_prime_change_order_batch. The description implies deletion, but does not explicitly state that this is for individual line items only, nor does it mention 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.