Delete a conversion funnel

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

Annotations already declare destructiveHint=true and idempotentHint=true, but the description adds valuable specifics beyond that: the deletion cascades to results history, it is irreversible, and it requires two distinct permissions. These details go beyond the safety profile annotations provide, though pagination/response behavior isn't discussed (and no output schema exists).

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?

Four short sentences, front-loaded with the irreversible destructive action, followed by permission and confirmation requirements. Every sentence earns its place with no filler.

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 single-parameter tool with strong annotations and no output schema, the description covers the critical pieces: cascade scope, irreversibility, permissions, and user confirmation. The only material omission is any guidance on the funnelId parameter itself.

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 schema has one required parameter (funnelId as a UUID) with 0% description coverage, and the description never mentions funnelId or clarifies its format. The single-parameter baseline would be higher, but with no compensating description this is a clear gap for the only input the agent must supply.

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 plus resource ('Permanently delete a funnel') and immediately scopes it to 'its results history,' distinguishing it from sibling tools like update_funnel or create_funnel. An agent can tell exactly what this tool does without inspecting the schema.

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?

It gives clear preconditions: both funnels:write and delete permissions are required, and the agent must confirm with the user before calling. It doesn't explicitly name an alternative tool such as update_funnel for non-destructive changes, but the destructive framing implicitly routes the agent away from it.

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