delete_pipeline

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

Annotations are absent, so the description carries the full burden of behavioral disclosure. It does convey that this is a destructive whole-pipeline deletion, but it does not disclose whether associated stages or leads are also deleted, whether the action is reversible, or what permissions are required.

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 one short, front-loaded sentence with no filler or redundant information. It is concise and easy to parse, though the brevity leaves out important behavioral details.

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 and no output schema, this description is incomplete. It does not explain cascading consequences, irreversibility, validation behavior, or any conditions that should be checked before calling it.

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 only 50%: client_slug has a description but pipeline_id does not. The description adds no parameter-level meaning, so the agent must rely on the parameter names alone to understand that pipeline_id identifies the pipeline to be deleted.

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 states a clear action ('Exclui' = deletes) and a specific resource ('funil de vendas inteiro' = entire sales pipeline). It also distinguishes itself from the sibling delete_pipeline_stage by emphasizing that it deletes the whole 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?

There is no guidance on when to use this tool versus alternatives. It does not mention prerequisites, such as whether the pipeline must be empty, or caution against using it when only a stage should be removed. The agent must infer usage from the tool name and high-level description.

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