Delete Commitment Contract

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

Annotations already indicate destructiveHint=true and idempotentHint=true, so the safety profile is known. The description adds 'This cannot be undone' and 'Permanently removes,' which reinforce permanence but are redundant. It also lists required parameters (already in schema) and the endpoint URL, which provides some context but does not cover authorization, rate limits, or response behavior.

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 relatively short but contains redundancy: 'permanently delete' appears twice, and 'This cannot be undone' is stated twice. It could be more concise by combining these statements. The inclusion of the full endpoint URL is useful but may be considered extraneous for an agent. Overall, it is acceptable but not optimally 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 simple delete operation with good annotations and full schema coverage, the description is adequate but incomplete. It lacks information about prerequisites (e.g., permissions), whether the deletion cascades to line items, or what the response looks like (likely a 200 or 204). The agent may need to infer these from the endpoint pattern.

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?

Input schema coverage is 100%, with each parameter having a clear description (URL path parameter, unique identifier). The description simply lists the required parameters without adding new meaning. Given the high schema coverage, the description adds minimal semantic value beyond what the schema already provides.

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 tool's purpose: 'Deletes a Commitment Contract for a given project.' It specifies the resource (Commitment Contract), the action (delete), and the scope. The name and title align, and it naturally distinguishes from siblings like delete_commitment_contract_line_item or delete_commitment_change_order by explicitly naming the contract entity.

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 provides no guidance on when to use this tool versus alternatives. It repeats 'Use this to permanently delete the specified Commitments' but does not mention alternative actions (e.g., editing vs. deleting, or using other delete tools for sub-resources). The agent is left to infer usage from the name alone.

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