delete_a_pipeline

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

Annotations already include destructiveHint=true; the description adds a user confirmation reminder but does not elaborate on side effects like cascading deletions or idempotency. No contradiction with annotations.

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 contains redundancy: 'Delete a pipeline' appears twice and 'Deletes a record' adds little value. Could be more concise without losing clarity.

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 tool with one required parameter and clear annotations, the description is adequate but could note any constraints (e.g., pipeline must exist) or return behavior.

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% with a clear description for the only parameter 'id'. The description does not add extra context beyond 'Pipeline's id', meeting the baseline.

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 'Delete a pipeline' and includes 'DESTRUCTIVE · deletes data · Deal Groups', making the action and resource unambiguous. It distinguishes from sibling delete tools by specifying the pipeline resource.

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?

Provides a safety guideline 'Confirm with the user before calling.' However, lacks explicit guidance on when to use versus alternatives or prerequisites (e.g., pipeline must have no active deals).

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