Delete Reminders

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

The annotation already marks destructiveHint: true, and the description adds 'This action cannot be undone,' which is critical behavioral context beyond the annotation. It discloses irreversibility but no other side effects, which is sufficient for a simple delete tool.

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 short sentences that are front-loaded with the action and include a crucial caveat about irreversibility. No wasted words.

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 one-parameter delete tool with a destructiveHint annotation and a clear reference to show output for indices, the description covers all necessary context. The lack of an output schema is acceptable for a destructive action, but it could have mentioned what happens to related data or confirmations.

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 schema already documents the 'ids' parameter with a matching description, so schema coverage is 100%. The description repeats the same information without adding new semantics, so the baseline 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 states the tool deletes reminders, with a specific verb ('delete') and resource ('reminders'). It differentiates from sibling tools like complete-reminders by emphasizing permanent removal, and the reference to index numbers from show output adds precise scope.

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 provides context that reminders are referenced by index numbers from show output or ID/UUID prefixes, implying a prerequisite viewing step. However, it does not explicitly contrast with alternatives like complete-reminders or state when not to use this tool.

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