Delete Prime Change Order Batch

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

Annotations already indicate destructiveHint=true. Description adds no new behavioral context beyond reiterating 'cannot be undone'. No mention of authorization, rate limits, or side effects beyond what annotations cover.

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?

Repetitive phrasing ('permanently delete' and 'This cannot be undone' repeated verbatim) and inclusion of API endpoint details not needed for tool selection. Could be shortened to one sentence.

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?

No output schema exists, but description does not mention return value or confirmation. Lacks prerequisites (e.g., permissions, status of batch). Incomplete for a destructive 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?

Schema has 100% coverage, so the description adds no value. It redundantly lists required parameters without adding constraints, formats, or relationships.

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 verb 'Delete' and resource 'Prime Change Order Batch' are clear, but the description incorrectly mentions 'Prime Contracts' instead of batches, causing confusion. Sibling tools like 'delete_prime_change_order' exist but are not 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?

The description states to use for permanent deletion but provides no guidance on when to use this tool versus alternatives (e.g., delete_prime_change_order, delete_commitment_change_order_batch). Missing 'when not to use' and prerequisites.

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