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

Annotations already declare destructiveHint=true, readOnlyHint=false and non-idempotency, so the safety profile is covered. The description adds genuinely new behavior beyond them: the deletion cascades to child stages and is gated by three invariants. It stops short of saying whether deletion is hard or soft, or what error surfaces when a guard trips.

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 sentences with zero filler; the action and its cascade come first, then the refusal conditions. Every clause carries information an agent needs.

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, single-parameter tool with no output schema, the description covers the essential facts: what is destroyed, what is destroyed alongside it, and when the call is illegal. Remaining gaps (failure behavior, required permissions, reversibility) are minor for a tool of this size.

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 only one parameter and schema description coverage is 100% ('The pipeline's id (from list_pipelines)'), so the schema already carries the semantics. The description adds no format or sourcing detail beyond it, making the baseline 3 appropriate.

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 and resource ('Delete a pipeline') and adds non-obvious scope: the cascade to 'its stages'. This clearly separates it from create_a_pipeline and save_a_pipeline in the sibling list, and an agent knows exactly what entity is affected.

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?

Explicitly enumerates three situations where the call must not be made ('Never the only pipeline, nor the default one, nor one that still holds open deals'), which is strong when-not guidance. It does not, however, point to an alternative workflow (e.g. reassigning deals or changing the default first), so the agent is told what blocks it but not how to proceed.

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