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

Annotations already declare destructiveHint=true and idempotentHint=false, so the safety profile is known; the description adds real value by naming the cascading deletions and stating irreversibility explicitly. It stops short of noting that the confirm flag must be true or that customerId is superadmin-only, both of which live only in the schema.

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 tight sentences, with the core action and cascade scope front-loaded before the destructiveness warning. No filler or repetition.

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 destructive mutation with full annotation coverage, complete schema descriptions, and no output schema, the description supplies everything needed to call it safely: scope, cascade, and irreversibility. The only gap is the missing routing hint versus stop_optimization.

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 description coverage is 100%, so processId, confirm, and customerId are fully documented in the schema. The description adds no syntax, format, or behavioral detail about the parameters themselves, so the baseline 3 applies.

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 uses a specific verb (delete) plus resource (optimization process) and enumerates exactly what is removed: activities, runs, candidates, feedback. The scoping statement ('authenticated customer') distinguishes it from any superadmin path and from non-destructive siblings like stop_optimization.

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?

It establishes context (permanent, irreversible deletion) but never says when to choose this over the sibling stop_optimization, nor when deletion is inappropriate. The destructive framing implies care, yet no explicit alternatives or preconditions are named.

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