Delete Pipeline

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

With no annotations, the description discloses the critical destructive behavior: permanently removes the pipeline configuration and may orphan pipeline items. This goes beyond a simple statement of deletion and warns of irreversible side effects, though it doesn't detail error handling or response behavior.

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 short sentences, front-loaded with the action, followed by a concise warning. No wasted words.

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 parameter, the description includes the essential purpose and the key risk, making it sufficiently complete. It doesn't cover alternatives, but given the simplicity and the warning, it serves the agent well.

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 covers the single parameter fully with a clear description ('The PipelineId to delete'). The tool description adds no additional meaning beyond the schema, so baseline 3 is appropriate.

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 uses a specific verb+resource ('Delete a pipeline') and clearly indicates scope ('from the account'). Among many sibling delete tools, it unambiguously targets pipeline, distinct from delete_pipeline_item or delete_pipeline_status.

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 on when to use this tool versus alternatives, prerequisites, or any exclusion criteria. The warning about permanent deletion provides caution but not decision guidance.

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