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

The description discloses the destructive action and error behavior, but without annotations it carries the full burden. It does not mention whether deletion is permanent, cascades to related stages or deals, or returns any confirmation payload.

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?

The description is two compact sentences with no redundant wording. Each clause adds useful information: the action, the permission requirement, and the 404 behavior.

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 simple delete operation with no output schema, the description covers the essential action, required permission, and error case. It omits only optional details like success response shape or cascading effects, which are not strictly necessary to invoke the tool 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 descriptions are only the parameter names, so the baseline is neutral. The tool description adds context like 'tenant CRM' and 'foreign or missing id' but does not explicitly define organization_id as the tenant identifier or clarify pipeline_id semantics beyond the self-explanatory name.

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 description clearly states the action ('Deletes'), the resource ('one pipeline'), and the scope ('from the tenant CRM'). It unambiguously distinguishes this tool from the sibling create, get, list, and update pipeline tools.

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?

The intended use is evident from the verb and resource, and the description adds the prerequisite 'crm:write on the organization' plus 404 behavior for foreign or missing IDs. It does not explicitly contrast with alternatives, but no plausible alternative exists for deleting a pipeline.

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