Delete Prime Contract Line Item

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

The description confirms irreversibility ('cannot be undone'), matching the destructiveHint annotation. It adds the endpoint and API version, but repeats the same warning twice without providing additional behavioral details beyond what annotations already indicate.

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 mostly succinct but contains redundancy ('This cannot be undone' repeated twice). It front-loads the action, but could be trimmed. The inclusion of the API endpoint is informative but not essential for an AI agent.

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?

Covers the core action and required parameters. Lacks details on success/error responses, permission requirements, or side effects beyond 'permanent removal'. Given the destructive nature and no output schema, more context would improve completeness.

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% and each parameter has a description. The description lists required parameters but adds no meaning beyond the schema. Baseline 3 is appropriate as the schema carries the burden.

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?

Clearly states it deletes a prime contract line item. However, it confusingly refers to 'specified Prime Contracts' instead of line items, slightly reducing precision. Still, the verb-resource combination is clear and distinguishes from sibling delete tools.

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?

Provides no guidance on when to use this tool versus alternatives. It only states 'Use this to permanently delete...' without specifying context or exclusions. No comparison with other delete operations (e.g., delete_prime_contract) is given.

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