Delete A Change Order Change Reason

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

Annotations already indicate destructive behavior, and the description reinforces 'cannot be undone'. However, it repeats the inaccurate phrase 'specified Change Orders' and does not disclose additional behavioral traits beyond what annotations provide. The description adds minimal value.

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 repetitive, stating 'This cannot be undone' and 'Permanently removes the specified Change Orders' twice. It could be more concise by merging redundant statements. The structure is front-loaded with the purpose but suffers from redundancy.

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 tool with no output schema, the description provides basic context including the endpoint and required parameters. However, it lacks explanation of the Change Order Change Reason concept, how to obtain the ID, or what happens upon deletion (e.g., return status).

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?

The input schema covers both parameters with descriptions, and the description merely lists required parameters. No additional meaning is added beyond the schema, aligning with the baseline for 100% coverage.

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 it deletes a specific Change Order Change Reason for a Company, distinguishing it from create/update/list siblings. However, there is a slight inconsistency when it says 'specified Change Orders' instead of 'Change Order Change Reasons', which could cause confusion.

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 basic parameter requirements but lacks guidance on when to use this tool versus alternatives, such as when not to delete or what preconditions are needed. No explicit usage context is given.

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