Delete a list (irreversible)

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

Annotations already mark destructiveHint=true, but the description adds the two-call confirmation process, the preview content (list name and game count), and the 'everything in it' scope. This is significant behavioral disclosure beyond boolean hints, especially for an irreversible operation.

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 sentences, front-loaded with 'IRREVERSIBLE,' no wasted words. Each clause adds value: the destructive scope, the confirmation requirement, and the preview behavior.

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 simple delete tool with a well-documented schema and annotations, the description covers the destructive nature, the confirmation workflow, and the scope, making it complete for an agent to invoke correctly. The absence of an output schema is compensated by the clear preview behavior.

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 covers both parameters at 100% with detailed descriptions, and the description summarizes the confirmation flow but does not add new information beyond the schema. The baseline of 3 is appropriate because schema coverage is complete and the schema already explains the token semantics.

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 a specific verb ('Deletes') and resource ('entire list and everything in it'), clearly distinguishing it from sibling create/reorder tools. The title also reinforces irreversibility, making the purpose unambiguous.

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 gives explicit step-by-step usage for the confirmation workflow: first call without a token, review preview, then call again with the token. It does not explicitly name alternatives, but the destructive context and confirmation instructions provide clear guidance on how to use it safely.

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