Delete Prime Change Order

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

The description warns 'This cannot be undone' multiple times, aligning with destructiveHint=true annotations. However, it does not clarify idempotency behavior (idempotentHint=true) or side effects. The repetition adds little beyond the annotations.

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 redundant ('cannot be undone' repeated) and includes extraneous metadata (API path). While informative, it could be trimmed without losing substance. Adequate but not exemplary.

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?

No output schema is provided, and the description does not mention return values, error conditions, or success indicators. For a destructive operation, more context on outcomes and idempotency would be beneficial.

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 the description merely restates required parameters without adding meaning beyond the schema's own descriptions. No additional semantics provided.

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 states 'Delete the specified Prime Change Order' with a clear verb and resource. It also distinguishes from siblings by mentioning it supports only 1 and 2 tier configurations, which differentiates it from batch or line item deletion 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?

The description provides a constraint ('only supports projects using 1 and 2 tier change order configurations') but does not explicitly guide when to use this tool versus alternatives like delete_prime_change_order_batch. Usage is implied but lacks explicit exclusions or comparisons.

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