delete_purchase_order

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

The description adds no behavioral context beyond what the annotations already provide. Annotations indicate destructiveHint=true, readOnlyHint=false, and idempotentHint=true, but the description does not disclose consequences, reversibility, or side effects. It simply restates the action.

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 extremely concise with no wasted words, but it is perhaps too sparse to provide any structural benefit like lists or caveats. For a simple delete operation, it is appropriately sized, but could include a bit more context without losing conciseness.

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 one-parameter delete tool with annotations indicating destructiveness and open-world side effects, the description is minimally viable. It doesn't mention what happens after deletion, whether it's permanent, or how it relates to related objects. With openWorldHint=true and no output schema, more context would aid the agent.

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% (purchase_order_id is described as 'the id of the purchase order'). The description adds no additional semantic value beyond the schema, so a baseline score of 3 is appropriate.

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 operation (delete) and the resource (purchase order), using a specific verb+resource structure. It is unambiguous and distinguishes this tool from sibling tools like update_purchase_order or get_purchase_order.

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 does not mention prerequisites, when not to use it, or compare with update_purchase_order or other delete_* tools. Usage is only implied by the verb 'delete'.

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