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

Beyond the annotations, the description discloses non-obvious side effects: isDefault moves the default away from the current default pipeline, a new pipeline is only visible to workspace admins until assigned, positions are stored as sent and never renumbered, and retrying with the same idempotencyKey returns the first result. It also notes the call touches only local config and sends nothing externally. Minor gap: it never warns about the destructive-creating nature flagged by destructiveHint, though the side effects it lists already imply real change.

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 and permission constraints are front-loaded, and most sentences carry distinct operational value. The confirmation block is somewhat repetitive ('Before you call it... Never infer the go-ahead... If any detail is your own guess...'), which could be tightened, but the length is defensible for a safety-critical, admin-only mutation.

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?

With no output schema, the description compensates by explaining that it returns the pipeline and its stage ids and that create_record/update_record consume them as pipelineId and pipelineStageId. Combined with permissions, idempotency, visibility, and side-effect notes, an agent has everything needed to invoke this correctly.

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 only 14% (just workspaceId), so the description must carry the load, and it does for the critical fields: pipelineType (DEALS/LEADS), stage position (counting from 0, stored as sent), outcomeCategory (WON/LOST on closers, OPEN elsewhere, lowest position must be OPEN), and isDefault semantics. It leaves confirm, color, winProbability, forecastCategory, and targetDurationDays unexplained, so a meaningful portion of the schema-level params remain undocumented beyond their types/enums.

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?

The opening sentence gives a specific verb and resource ('Creates one deal or lead pipeline with its stages, in order') and scopes it to a single new pipeline, distinguishing it from add_pipeline_stage and update_pipeline without requiring the schema. An agent can identify the tool immediately.

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?

Explicit prerequisites and exclusions are given: only a workspace admin may call it and anyone else is refused, plus a clear confirmation protocol (state exactly what will be created, get go-ahead in the same turn, never infer it from an earlier message or a plan). This is unusually complete when-to-use guidance for a mutation tool.

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