openpanel_delete_funnel

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It fails to indicate whether this is a permanent/hard delete versus soft-delete, whether the operation is atomic, or what error conditions might occur. Only the verb 'Delete' hints at destructiveness.

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?

While brief and front-loaded with the action, the '[UNIFIED]' decorative prefix wastes space without conveying useful metadata. The single-sentence structure is efficient but overly reductive given the complete absence of schema documentation.

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 operation with zero schema descriptions and no annotations, the description is inadequate. It omits parameter semantics, return value structure (success confirmation), irreversibility warnings, and relationship between the three required identifiers.

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% for all three parameters (site, project_id, funnel_id). The description provides no semantic context to compensate—no explanation of what 'site' refers to (domain vs. ID), how project_id relates to funnel scoping, or expected formats.

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 the specific action (delete) and resource (funnel), providing clear intent. However, it fails to differentiate from sibling tools like openpanel_create_funnel or openpanel_update_funnel, and the '[UNIFIED]' prefix adds no meaningful context for tool selection.

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?

Provides no guidance on when to use this tool versus alternatives (e.g., update_funnel for modifications), nor does it mention prerequisites like requiring admin privileges or warnings about data loss inherent in deletion operations.

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