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

No annotations are provided, so the description carries the full burden of behavioral disclosure. Saying 'delete' implies a destructive operation, but the description does not state whether deletion is permanent or reversible, whether it cascades to associated stages or deals, whether it is idempotent, or what permissions are required. For a destruction tool this is a significant gap.

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 three words with zero wasted content, and the action is front-loaded. However, it is so minimal that it borders on under-specification — there is no information beyond what the tool name already conveys, so the description earns little independent value.

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, no annotations, and only a terse description, the tool is incomplete for a destructive operation. An agent would not know what the call returns on success/failure, whether deletion is permanent or cascades, or any safety considerations. The simple 2-parameter schema lowers the bar, but a deletion tool should disclose side effects.

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 100% (both pipeline_id and organization_id have descriptions), so the schema already documents the parameters. The description adds no additional meaning about how the parameters relate (e.g., that pipeline_id is scoped within organization_id or how to obtain valid IDs). Baseline 3 applies because the schema carries the load.

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 'delete CRM pipeline.' uses a specific verb (delete) and resource (CRM pipeline), clearly identifying the operation. It inherently distinguishes from sibling tools like commsharbor_crm_pipelines_create, _get, _list, and _update, since 'delete' states the exact action. However, it gains no additional precision from the title (null) and offers no elaboration on what a pipeline deletion entails.

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?

No guidance is provided on when to use this tool versus alternatives. The description does not mention prerequisites, exclusions, or distinguish this from other delete tools in the sibling set (e.g., crm_pipelines_delete vs crm_stages_delete vs crm_deals_delete). An agent must infer usage entirely from the tool name.

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