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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is covered. The description adds genuine value by warning that deals attached to the pipeline must be moved or closed first, implying a cascade or a block on deletion. It stops short of stating whether deletion is permanent, what happens to unmoved deals, or whether confirmation is required.

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, no filler, with the action front-loaded ahead of the precondition. Nothing is wasted, though the second sentence could be slightly more concrete about the consequence of ignoring it.

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 core action and the main hazard. It is still thin on irreversibility, failure modes when dependent deals exist, and how to obtain the pipeline ID, which an agent needs before calling a permanent delete.

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 0%, and the description says nothing about pipelineId, so it adds no meaning beyond the schema. The single parameter is self-explanatory by name, but the description misses an easy win by not pointing to list_pipelines as the source of the ID.

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 sales pipeline"), which cleanly distinguishes it from the many other delete_* siblings that target deals, projects, quotes, and so on. It does not explicitly name a sibling it is not, but the resource noun does the differentiation work.

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?

"Move or close its deals first" gives a precondition, which is real usage guidance for a destructive operation. However, it never says when to delete versus updating via update_pipeline, nor does it point at move_deal_stage / mark_deal_won / mark_deal_lost as the actions implied by "move or close".

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