Delete Pipeline Items (Bulk)

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

With no annotations provided, the description carries full responsibility for behavioral disclosure. It effectively communicates the destructive nature ('Delete'), key constraints (same pipeline, max 5000 items), and the return value (count of processed and skipped items). It lacks explicit irreversibility warnings or permission requirements, but provides sufficient context for safe use.

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 sentences, front-loaded with the primary action, and every sentence adds value: what it does, a key constraint, a limit, and the return format. There is no redundant or filler content.

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 no output schema, the description explains the return value (count of processed and skipped items). It covers the essential aspects for a bulk delete tool: target, constraint, limit, and result. Minor gaps include potential error conditions or what 'skipped' means, but overall it is adequately complete for the tool's complexity.

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%, so the schema already documents both parameters ('pipeline_id' and 'pipeline_item_ids'). The description essentially restates the constraint that all items belong to the same pipeline and the 5000 max, which are already in the schema. It adds no meaningful semantic information beyond the structured fields.

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 ('Delete multiple pipeline items at once'), the resource ('pipeline items'), and the system ('Less Annoying CRM'). It distinguishes itself from the sibling 'delete_pipeline_item' by emphasizing the bulk nature, making the purpose unambiguous.

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 description implies the appropriate use case (deleting multiple items at once) and provides constraints (all items must belong to the same pipeline, max 5000 per call). It does not explicitly name alternatives or exclusion criteria, but the context is clear enough for an agent to differentiate this from single-item deletion.

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