voice_delete_pipeline

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

No annotations are provided, so the description must fully disclose behavioral traits. While 'Delete' implies a destructive action, the description lacks details on irreversibility, side effects, permission requirements, or error handling. The constraint about the preferred pipeline is helpful but insufficient for full transparency.

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 concise, consisting of two short sentences that convey the core action and a key constraint without any extraneous 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?

The description covers the essential usage constraint and the core purpose. While the output schema exists (so return values need not be explained), the description could still mention prerequisites beyond the preferred pipeline constraint, but it is minimally adequate for a simple delete tool.

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?

The input schema has one parameter ('pipeline_id') with no description, and the tool description provides no additional meaning or context for this parameter. With 0% schema description coverage, the description fails to compensate.

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 an Assist pipeline' and adds a specific constraint about the preferred pipeline, making it distinct from sibling tools like voice_create_pipeline or voice_update_pipeline.

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 explicitly states a condition for use: 'Cannot delete the preferred pipeline — change preference first.' This provides clear guidance on when not to use the tool, though it does not elaborate on alternatives beyond the implied prerequisite.

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