Delete A Prime Contract Line Item

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

The description provides significant behavioral context beyond the annotations: permanence ('This cannot be undone'), idempotency behavior ('a repeat call returns 404'), and failure modes with HTTP status codes (401, 403, 404). This is exactly the kind of information an agent needs to safely invoke a destructive operation, and it complements the destructiveHint=true and idempotentHint=true annotations without contradiction.

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 moderately sized and reasonably front-loaded, starting with the action. It includes necessary details (prerequisites, permanence, errors, endpoint) but has some redundancy: 'Delete a Line Item' and 'Permanently removes' overlap, and 'Confirm' and 'resolve' make similar points. Slight tightening could improve it, but it is not excessively verbose.

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 delete operation with no output schema, the description covers the essential context: prerequisites, permanence, error handling, and the exact API endpoint. It does not describe the success response, but for a delete that is often an empty response and less critical. Overall, it sufficiently equips the agent to invoke the tool correctly.

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?

Although schema coverage is 100% (baseline 3), the description adds a meaningful constraint: 'prime_contract_id, id must identify existing parent records — resolve them with the matching list tool first.' This clarifies the expected relationship and validity of the parameters beyond the schema's basic type and location descriptions. It also confirms the required parameters list.

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 action with a specific verb and resource: 'Delete a Line Item from the Prime Contract' and 'Permanently removes the prime contract line item.' It also identifies the exact endpoint, distinguishing this from list/show/update tools. No ambiguity remains about what the tool does.

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 gives explicit prerequisites: 'Confirm the target id with the matching show or list tool before calling' and 'resolve them with the matching list tool first.' This tells the agent when to use this tool (after listing/showing) and how to obtain valid IDs. It does not explicitly name alternative tools for update/creation, but the context is clear enough.

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