delete_reminders

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

Annotations indicate destructiveHint=true, so the description adds no new behavioral context. It does not disclose cascading effects, permission requirements, or what happens after deletion (e.g., no confirmation or undo).

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 extremely concise (two words) but lacks necessary detail. It is not wasteful, but it does not earn its place by providing any information beyond the tool name.

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 tool with no output schema and destructive behavior, the description should explain outcomes and side effects. It fails to complete the context, leaving the agent unsure about post-deletion state or confirmation.

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% with the parameter 'reminders_ids' well-documented as comma-separated. The description does not elaborate on the parameter, so no additional value is provided 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?

Description states 'Deletes reminders' which is clear but lacks scope or differentiation from sibling delete tools (e.g., delete_bank_accounts, delete_contacts). It is a tautology of the tool name and does not specify which reminders or filtering criteria.

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 use this tool versus alternatives like update_reminder or list_reminders. There is no mention of prerequisites, such as needing existing reminder IDs or confirmation before deletion.

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