Delete a specific stage from a sales pipeline by passing pipeline ID, status ID, and client slug, ensuring your funnel accurately reflects the sales process.
Exclui uma etapa específica de um funil.
| Name | Required | Description | Default |
|---|---|---|---|
| status_id | Yes | ||
| client_slug | Yes | Identificador do cliente (slug) | |
| pipeline_id | Yes |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden of behavioral disclosure. It conveys that the action is a deletion but does not mention irreversibility, potential impact on associated data, required permissions, or side effects.
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 a single clear, front-loaded sentence with no filler. Every word contributes meaning, and the verb-object relationship is immediately visible.
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 mutation with three required parameters, no output schema, and no annotations, this description is too sparse. An agent still lacks enough information about parameter semantics, prerequisites, and consequences to invoke it confidently.
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 description coverage is only 33%, and the description does not compensate. It does not explain that status_id likely identifies the stage, what pipeline_id refers to, or how client_slug scopes the operation.
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 ('Exclui' – deletes) and a specific resource ('etapa específica de um funil' – a pipeline stage). This clearly distinguishes it from siblings such as delete_pipeline, create_pipeline_stage, and update_pipeline_stage.
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 states only what the tool does and gives no guidance on when to use it versus alternatives like delete_pipeline. No context, prerequisites, or exclusions are provided.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.