Delete Pipeline Item

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

No annotations are provided, so the description carries the full burden. It explicitly warns that the deletion permanently removes the item, which is critical irreversible-destruction context. It does not mention auth, cascading effects, or error behavior, but the permanence warning covers the most important behavioral trait for a delete operation.

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 extremely concise: two sentences plus a required-field note, with the warning placed prominently. Every part contributes value, and the structure is clean and front-loaded.

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?

Given the tool's simplicity (one parameter, no output schema, no annotations), the description adequately covers the action, permanence warning, and required parameter. It does not mention the bulk alternative or error/return details, but for this simple delete operation those are not essential.

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 100% and the schema already describes pipeline_item_id as 'The PipelineItemId to delete'. The description repeats that it is required but adds no extra semantic meaning beyond the schema, so the baseline score of 3 applies.

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 verb (Delete), resource (pipeline item), and scope (single, from Less Annoying CRM). The 'single' qualifier effectively distinguishes this tool from the sibling delete_pipeline_items_bulk.

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 'single' wording implies usage for deleting exactly one item, hinting at the existence of a bulk alternative. However, there is no explicit statement of when to use this vs. delete_pipeline_items_bulk or other delete tools, so guidance remains implicit.

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