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

Annotations already declare destructive=true and idempotent=true; the description adds real value beyond them by spelling out exactly what is destroyed (a stage left out is removed) and a guard condition (a stage holding an open deal survives). It still omits error/response behavior and any auth prerequisites.

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?

Three tightly packed sentences front-load the core action and then the diff rules; every clause carries meaning, though the em-dash construction is dense enough to require a careful read.

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, no-output-schema mutation tool, the description supplies the essential replacement rules and the open-deal exception. Return-value expectations and validation failures are the remaining, minor gaps.

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?

With only 25% schema description coverage, the description compensates well: it explains the id-keep / no-id-add / omitted-remove semantics for stages and the open/won/lost kind. It says nothing about is_default or how pipeline_id is obtained, leaving a little schema burden unresolved.

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+resource ('Save a pipeline') and immediately scopes it as a full-editor-style replacement, distinguishing it from create_a_pipeline/delete_a_pipeline without opening any schema.

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 phrase 'as its editor does' plus the stage-diff rules make clear this is a whole-pipeline replace, so the caller knows the entire stage list must be supplied. It stops short of naming sibling alternatives or explicit when-not-to-use conditions.

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