Delete Purchase Order Contract

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

Annotations already include destructiveHint=true and idempotentHint=true. The description repeats 'permanently delete' and 'cannot be undone' but adds no new behavioral context beyond the annotations. It does not disclose any side effects, authorization requirements, or error conditions.

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 short but contains redundant phrases (e.g., 'permanently delete' and 'cannot be undone' repeated). It front-loads the purpose but could be more concise while retaining essential information.

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 tool with no output schema, the description covers the core action and required parameters. However, it lacks contextual details like prerequisites, permissions, or effects on related data, which would improve completeness given the complexity of the domain.

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 both parameters are well-described in the input schema. The description merely lists required parameters without adding semantic value or examples, so it meets the baseline but does not enhance understanding.

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 (delete) and the resource (purchase order contract). However, it does not differentiate from sibling delete tools like 'delete_commitment_contract' or 'delete_purchase_order_contract_line_item', which could lead to confusion. The reference to 'Commitments' clarifies the domain but duplicates phrasing.

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. It does not mention prerequisites, appropriate contexts, or when not to use it. For a destructive action, this omission is notable.

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