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

Annotations already declare destructiveHint=true, idempotentHint=true and readOnlyHint=false, so the safety profile is covered structurally. The description adds the required change_orders:write scope, which is auth context the annotations do not carry, though it says nothing about cascade effects or what the call returns.

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?

Two short sentences, action front-loaded, zero filler. Nothing could be removed without losing 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 an atomic one-parameter delete whose safety profile is fully expressed in annotations, the definition is essentially complete. It stops short of noting side effects (e.g. dependent records) or confirming deletion of a non-existent ID, but those are minor for this tool.

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?

There is a single parameter whose schema description coverage is 100% ('Change order ID'), so the schema already documents it fully. The description's 'by ID' adds no format or constraint detail beyond what is structured, matching the baseline 3 for high schema 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?

States a specific verb (Delete) plus the exact resource (change order) and the identifier to supply (by ID). Among the many sibling delete_* tools it is unambiguous which entity this targets, and it is clearly distinct from update_change_order and list_change_orders.

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 gives no when-to-use guidance, no conditions under which deletion is appropriate, and no alternatives (e.g. update or archive). The only prerequisite mentioned is the API scope, which is an authorization requirement rather than a usage heuristic.

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