Delete a VWO custom widget

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

The description adds significant behavioral context beyond annotations: it specifies the deletion is permanent, irreversible, and will break linked campaigns. This complements the destructiveHint and idempotentHint annotations with concrete details.

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 extremely concise (two sentences) with no fluff. Every sentence serves a purpose: stating the action/consequence and providing a usage instruction. Ideal for quick comprehension.

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 deletion tool with clear side effects and no output schema, the description is complete. It covers the essential behavioral details (irreversibility, impact on campaigns, need for confirmation).

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 100%, so the description does not need to elaborate on parameters. It adds only a brief mention to confirm the widget, but no additional parameter-level meaning beyond what the schema already provides.

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 clearly states the action ('Permanently delete a custom widget') and the resource, distinguishing it from sibling tools like vwo_new_custom_widget or vwo_update_custom_widget. It also emphasizes the irreversible nature and consequences.

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 instructs to confirm with the user first, ensuring appropriate context. The schema description for widgetId provides guidance to use vwo_list_custom_widgets if needed. However, it does not explicitly exclude scenarios where a soft-disable might be preferred over deletion.

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