deleteWidget

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

Exceeds annotation's destructiveHint by detailing side effects like broken shortcodes and recommends auditing with listWidgets, adding significant value.

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?

Well-structured with bold headings, bullet points, and separate sections for usage, caveats, and see also. Every sentence adds value without redundancy.

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?

Comprehensively covers purpose, destructive nature, prerequisites, side effects, output format, and alternative, leaving no obvious gaps.

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?

Only mentions that widget_id is required, which is already in schema. With 0% schema coverage, minimal additional semantic value is provided, but the parameter is self-explanatory.

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?

Clearly states verb 'Delete' and resource 'widget', and distinguishes from sibling 'updateWidget' by mentioning an alternative for disabling.

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?

Explicitly provides when to use (removing unused widget) and when not to use (disable via updateWidget), along with a practical alternative and an audit suggestion.

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