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

Annotations only flag non-read-only, non-idempotent, closed-world; the description adds the destructive specifics that matter: stages left out are removed, their open deals move to the first stage, and named stages retain their deals. The 'Old name => New name' rename path and the advice to disclose deal movement before calling are exactly the behavioral context an agent needs before a mutating call.

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?

Front-loads the two operations, then the consequences, then the prerequisite—every sentence carries information. Sentences are long and multi-clause, which slightly taxes parsing, but nothing is redundant.

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 non-idempotent mutation with no output schema, the description covers consequences, rename semantics, stage removal, and a pre-call check. It omits permission/auth requirements and any hint about result confirmation, which are minor remaining 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?

Schema coverage is 67% and the description meaningfully extends it: 'stages' is the FULL ordered list, 'new_name' is the rename target, and the rename syntax explains how a stage keeps its deals. The 'pipeline' parameter's id-vs-name distinction is left to the schema, so it is not a complete semantic layer.

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?

Specific verb+resource ('Rename a pipeline and/or replace its stages') that clearly distinguishes it from siblings like crm_create_pipeline, crm_delete_pipeline, and crm_pipelines. The scope (rename and/or restructure) is stated immediately in the first clause.

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?

Gives a concrete prerequisite ('Get the current stages from crm_pipelines first') and an operating instruction ('tell the person which deals will move before calling'). It does not explicitly route to alternatives such as crm_create_pipeline for new pipelines, so it falls just short of a full when/when-not map.

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