delete_reminder

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

Annotations already mark this as destructive and idempotent, but the description adds critical non-obvious behavior: for task-owned reminders, only the server-side entry is removed and the task document's reminder fields remain, so the app may recreate it. This goes well beyond the annotations and clarifies exactly what is and isn't destroyed.

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 efficient sentences: the main action is front-loaded, and the essential caveat follows immediately. Every sentence earns its place with 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 single-parameter delete tool with an output schema and annotations covering destructiveness and idempotency, the description is fully complete. It covers the main use case, the edge case with task reminders, and how orphaned entries relate to get_reminders.

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%, so the baseline is 3. The description adds meaningful context about which reminder IDs are valid targets (standalone 'M' reminders versus task-linked reminders), though it doesn't add format or syntax details beyond the schema.

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?

States a specific verb and resource: 'Delete one or more server-side reminders.' It also distinguishes itself from sibling tools like set_reminder and get_reminders by clarifying the scope (server-side entries) and target type (standalone 'M' reminders).

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 instructs when to use the tool: prefer against standalone reminders (type 'M') or orphaned entries from get_reminders. It also warns against relying on it for task-linked reminders, since the app may recreate them—giving clear selection criteria and exclusions.

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