delete_pipeline

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

With no annotations provided, the description must fully disclose behavior. It states the tool deletes a pipeline and its execution history, but omits critical details such as irreversibility, required permissions, impact on related data, or confirmation steps. This is insufficient for a destructive 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 at three lines, front-loaded with the main action. Every sentence is necessary: purpose, parameter argument, and return value. No redundancy or extraneous text.

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 one-parameter tool with an output schema, the description covers the essential aspects: action, input, and return. However, it could improve by noting permanence or confirmation behavior, especially given the lack of annotations. Overall, it is nearly complete.

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 description includes an Args section that fully explains the single required parameter 'name' as 'Name of the saved pipeline to delete.' Despite the schema coverage signal being 0%, the parameter is clearly documented within the description, adding complete meaning beyond the schema.

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 explicitly states 'Delete a saved pipeline configuration and its execution history,' providing a specific verb and resource. The name itself is unambiguous, and it clearly distinguishes from sibling tools like list_pipelines, save_pipeline, and load_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 offers no guidance on when to use this tool versus alternatives, such as manage_pipeline or schedule_pipeline. It does not specify prerequisites or when not to use it, leaving the agent without contextual decision support.

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