deleteSmartList

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

Builds on annotations by detailing permanence, irreversibility, no soft-delete, and needed user confirmation for bulk use. No contradictions.

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?

Structured with clear headings ('Use when', 'Required', 'See also', 'Destructive', 'Returns'), every sentence is informative, no fluff.

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?

Covers all necessities: purpose, parameter, behavior, return value, and alternative. Completes the tool's picture despite lacking output schema.

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 single parameter 'smart_list_id' is explained by context ('by ID') and labeled as required. Despite 0% schema coverage, the description provides sufficient meaning.

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 'Delete a smart list' with specific verb and resource, and distinguishes from sister tools like updateSmartList. The scope 'by ID' is explicit.

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 explicit use case: 'when removing a saved filter configuration', and directly references an alternative: 'updateSmartList (modify without removing)'.

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