delete_funnel

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

No annotations are provided, so the description carries the full burden. It clearly discloses the most critical behavioral trait: irreversibility ('Permanently delete' and 'Irreversible'). It stops short of describing permissions, error handling, or scope of deletion, but for a simple delete tool, this is solid coverage.

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?

Two short sentences, with the action front-loaded and the warning immediately following. Every word earns its place, and the structure is highly efficient.

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?

Given the simple one-parameter nature, the presence of an output schema, and the explicit irreversibility warning, the description is nearly complete. It could add details about permissions or failure outcomes, but these are not essential for a straightforward delete tool. The guidance to list first adds valuable context.

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 0%, so the description must compensate. It indirectly explains funnel_id by saying 'by id' and recommending list_funnels to confirm the id. However, it does not explicitly describe the id format or provide details beyond the schema's title. For a single, self-explanatory parameter, this is adequate but not outstanding.

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 exactly what the tool does: 'Permanently delete a trace funnel by id.' It uses a specific verb (delete), identifies the resource (trace funnel), and clearly distinguishes from sibling tools like list_funnels and create_funnel.

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?

Explicit guidance is provided: 'Use ``list_funnels`` first to confirm you have the right id.' This tells the agent when to use this tool relative to an alternative and even gives a prerequisite step, making usage clear.

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