Delete Reminder List

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

Annotations include destructiveHint: true, and the description adds 'This action cannot be undone,' reinforcing irreversibility beyond the annotation. It also specifies that all reminders are deleted, which is a destructive consequence. This is useful behavioral context, though it does not cover potential permission requirements or other edge cases.

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 two sentences and 15 words, immediately stating the action and its consequence. It is front-loaded with the key verb and resource, and every sentence adds value. There is no extraneous information.

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 one-parameter destructive tool with annotations covering the safety profile, the description is complete. It covers the action, the scope (list plus reminders), and irreversibility. No output schema exists, but none is necessary given the simplicity. The description provides all needed context for an AI agent to use the tool correctly.

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 coverage is 100% for the 'name' parameter, with a description 'Name of the list to delete.' The tool description does not add any additional parameter semantics beyond the schema, so the baseline score of 3 is appropriate.

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 identifies the tool's function: 'Delete a reminder list and all its reminders.' It uses a specific verb and resource, and the note about deleting all reminders distinguishes it from sibling tools like delete-reminders, which handles individual reminders. This is a clear and unambiguous purpose statement.

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?

The description implies usage for deleting an entire list, but it does not explicitly state when to use this tool versus alternatives like delete-reminders. No exclusions or alternative tools are mentioned. The context is clear about the scope, but lacks explicit guidance on choosing this tool over others.

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