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

Goes well beyond the annotations by disclosing the duplicate-name behavior (nothing is created, existing pipeline is returned with created=false, and that is the only distinguishing field), the case-insensitive uniqueness rule, the default-pipeline side effect, and that won/lost stages are appended at the end. These are exactly the non-obvious behaviors an agent must know before invoking.

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?

Purpose is front-loaded in the first sentence and the remaining sentences each carry distinct operational detail (stage ordering, defaults, duplicate handling, next steps). It is long for a four-parameter tool, and the capitalized duplicate-name warning plus the 'do not add a number to the name' admonition are slightly verbose, but no sentence is purely 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 creation tool with no output schema and no annotations beyond safety hints, the description covers the seeded defaults, uniqueness constraint, idempotent-failure semantics, default-pipeline effect, and follow-up calls. An agent has everything needed to call it correctly and interpret the result, including the created flag.

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 100%, so the schema already documents parameter names, types, and bounds. The description still adds meaning the schema lacks: stages are in left-to-right board order with worked examples, won_stage_name/lost_stage_name are only honored when stages is passed, and names must be unique ignoring case. Minor gap: it does not restate the 1–15 item bound, but that is in the schema.

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 ('Create a deal pipeline') in the first phrase, and distinguishes itself from sibling stage-editing tools by naming rename_pipeline_stage, create_pipeline_stage, delete_pipeline_stage and reorder_pipeline_stages as the alternative for modifying an existing pipeline.

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 says most accounts need only one pipeline and directs the agent to the stage-editing siblings instead of creating a second one. It also prescribes the next step after creation (pass pipeline_id to create_deal or call set_default_pipeline), so when-to-use and what-to-do-next are both covered.

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