Delete purchase order by identifier.

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

Annotations already mark destructiveHint=true and idempotentHint=true. The description adds the behavioral detail that non-integer IDs or values >1000 cause API errors. This is consistent and provides some extra context, but does not fully disclose error responses or side effects.

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 two sentences and front-loaded with the key constraint. It is concise and to the point, though it could be slightly more 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 one parameter and existing annotations, the description covers the primary gotcha (valid ID range). No output schema exists, but the description is adequate. It could mention success response or behavior, but overall complete enough.

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 covers 100% with a description for orderId. The description adds value by specifying expected valid integer IDs (<1000) to avoid errors, which helps the agent choose appropriate values.

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 title 'Delete purchase order by identifier' clearly states the action and resource. The description reinforces by focusing on valid IDs for deletion. However, it does not differentiate from sibling delete tools like delete_pet or delete_user, so purpose is clear but lacks sibling distinction.

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 only provides a hint about valid IDs (<1000) but gives no guidance on when to use this tool vs alternatives. With multiple delete siblings, the lack of usage context is a significant gap.

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