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

With no annotations, the description carries the full burden and covers several non-obvious traits: default stages are auto-created as a side effect, the operation is restricted to workspace admins/owner, and it consumes no credits. It omits what happens on duplicate names, whether the new pipeline is returned with its id, and reversibility (though a sibling delete_crm_branch exists).

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?

Four short, telegraphic sentences with zero filler; the core action comes first, then visibility semantics, permissions, and cost. Every clause carries distinct information.

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 two-parameter mutation with no annotations and no output schema, the description covers the crucial gaps: permission gate, side effects, cost, and visibility model. The only thing an agent might still want (whether the created branch/id is returned) is unaddressed, but no output schema exists to imply it.

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 50%, so the description meaningfully compensates by explaining that member_user_ids controls visibility and that the General pipeline stays open to all users. The `name` parameter is left unstated, but its constraint (1-120 chars) is already in the schema and its meaning is self-evident.

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 an isolated pipeline (team / direction / client)') and clarifies the branch/pipeline naming ambiguity, which is the main confusion risk in this tool family. It does not name a sibling it differs from (e.g., crm_create_stage for adding stages, crm_update_branch for changes), so it falls short of maximum differentiation.

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?

'Workspace admins/owner only' gives a prerequisite, and 'General stays open to all' hints at when member_user_ids matters. However, there is no explicit guidance on when to create a new pipeline versus using an existing one, nor any pointer to sibling tools such as crm_create_stage or crm_update_branch.

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