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

The description adds substantial context beyond destructiveHint=true: it states that deletion cascades to stages, is permanent, cannot be undone, and is guarded by preconditions. It also explains the refusal behavior and the two-step confirmation workflow.

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 front-loaded with the core action, then lists the safety preconditions, then the irreversible consequence, then the confirmation workflow. Every sentence adds operational value with no filler.

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 no output schema, the description covers the action, cascade behavior, safety preconditions, refusal behavior, irreversibility, and the required confirmation sequence. An agent has enough information to call it correctly without further inference.

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 both parameters are already fully documented in the input schema. The description reinforces the confirm workflow but does not add parameter-level details beyond what the schema already provides.

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 and resource: 'Delete a pipeline and its stages.' This scope also implicitly distinguishes it from delete_pipeline_stage by making clear that this tool removes the entire pipeline including its stages.

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 gives explicit when-not conditions: not the default, no deals, no automation rule moves deals into it, and no website form files deals into it. It also tells the agent how to resolve the default-pipeline case ('make another one the default first') and notes that refusals explain what to fix.

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