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

With no annotations, the description carries the load well: it discloses irreversibility, the side effect on leads (reassigned to General rather than deleted), and the permission requirement. It stops short of saying what happens on attempting a default pipeline (error vs. silent refusal), so a 4 rather than 5.

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 clauses, each carrying distinct decision-relevant information: constraint, side effect, reversibility, authorization, and sequencing. Nothing 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 an irreversible mutation with no annotations and no output schema, the description covers the critical decision facts (non-default only, lead fate, approval gate). Minor gap: no mention of failure behavior for default pipelines or what the response confirms.

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?

One parameter at 100% schema coverage, so the schema already documents the UUID branch id. The description adds no format detail, but for a single-parameter tool the baseline is 4.

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 plus resource ('Delete a non-default pipeline'), with an explicit scope qualifier that separates it from crm_update_branch, delete_crm_stage, and the sibling preview_delete_crm_branch.

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?

States prerequisites explicitly: only non-default pipelines, admin/owner only, and only after the user approved preview_delete_crm_branch. That is a when-to-use gate and effectively names the required alternative path.

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