delete_reminder

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

No annotations are provided, so the description carries the full behavioral burden, yet it says nothing about permanence/reversibility, required permissions, or what happens to subtasks attached to the reminder. Only the implicit destructiveness of the verb 'Delete' conveys any behavioral information.

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?

A single short sentence with the operation and key front-loaded; nothing is wasted. It is efficient, though the brevity borders on under-specification for a destructive operation.

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?

An output schema exists so return values need not be explained, but for a destructive tool with zero annotations the definition should still cover irreversibility, permissions, or side effects. None of that is present, leaving the agent under-informed for a delete operation.

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 description coverage is 0% and the single 'id' parameter has no description, so the description must compensate. 'By id' at least clarifies that the identifier refers to a reminder (not a list or calendar), but it omits the id format, where the id comes from (e.g., list_reminders), and any error behavior for unknown ids.

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 a reminder') plus the lookup key ('by id'), which cleanly distinguishes it from delete_event, delete_note, and delete_calendar in the sibling list. It does not, however, differentiate itself from complete_reminder or update_reminder as an alternative way to handle a reminder.

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?

No guidance on when to delete versus archive or complete a reminder, no prerequisites, and no mention of related siblings like complete_reminder or bulk_reminders. The agent must infer all usage context from the name alone.

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