Delete A Prime Contract Line Item

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

The description emphasizes permanence, which aligns with the destructiveHint annotation. It does not contradict annotations, but it neither clarifies idempotency nor discusses potential error states (e.g., deleting an already deleted item).

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 front-loaded with the core action but suffers from repetition (e.g., 'cannot be undone' stated twice). It remains relatively concise and structured.

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 tool with no output schema, the description should explain the result of a successful deletion or error responses. It provides basic endpoint info but lacks outcome context.

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%, so the schema fully documents each parameter. The description merely repeats the required parameters without adding meaning or usage details.

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 verb 'Delete' and the resource 'Line Item', but the phrase 'specified Prime Contracts' is inaccurate (should be 'Line Items'). It distinguishes from many sibling delete tools by specifying 'Prime Contract Line Item', but no explicit differentiation from the identically named sibling 'delete_prime_contract_line_item'.

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 alternatives (e.g., other delete tools for line items). It only lists required parameters, offering no context about prerequisites or scenarios.

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