delete_pipeline

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

The description mentions the requirement for BAIC_ALLOW_DESTRUCTIVE=true, but provides no detail about the destructive nature, irreversibility, or side effects. With no annotations, the description carries full burden and falls short.

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, using two short sentences with no wasted words. It communicates the essential action and requirement efficiently.

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 destructive tool with no annotations, output schema, or parameter explanation, the description is too sparse. It fails to convey the consequences of deletion or any additional context needed for safe invocation.

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 does not mention the pipeline_id parameter at all. Schema description coverage is 0%, so the description should compensate but does not, leaving the agent without any guidance on how to specify the parameter.

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') and the resource ('a pipeline'), making the tool's purpose unambiguous. There is no other sibling tool that deletes pipelines, so it is adequately distinguished.

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 is given on when to use this tool or how it compares to alternatives. The only added context is the BAIC_ALLOW_DESTRUCTIVE=true requirement, which is a prerequisite rather than usage guidance.

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