delete_reminder

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

Beyond the destructiveHint and idempotentHint annotations, the description discloses an important side effect: for task reminders, only the server-side entry is removed and the task's reminder fields remain, allowing the app to recreate it. This is exactly the kind of behavioral detail an agent needs to avoid incorrect expectations.

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 compact and front-loaded: the main action is stated first, then the caveat and usage preference follow. Every sentence adds meaningful information with no filler or repetition.

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 destructive delete operation, the description covers what is deleted, what is not deleted, when it is safe to use, and where to get the target IDs. Combined with the output schema and annotations, an agent has enough context to invoke it correctly and anticipate side effects.

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 reminder_ids as 'IDs of reminders to delete,' so the baseline is 3. The description adds useful semantic guidance by specifying that IDs should be standalone reminders or orphaned entries from get_reminders, which helps the agent select valid inputs rather than task-associated reminders.

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 opens with a specific verb and resource: 'Delete one or more server-side reminders.' It clearly distinguishes the server-side behavior from task-document reminder fields and references standalone reminders of type 'M', making it easy to tell apart from broader task deletion operations.

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 gives explicit usage guidance: prefer deleting standalone reminders or cleaning up orphaned entries from get_reminders, and warns against relying on it for task reminders because the app may recreate them. This tells the agent when to use the tool and when the result may be incomplete.

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