Delete Reminder

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

Annotations already declare destructiveHint: true and idempotentHint: true, so the destructive nature is known. The description adds a mode constraint 'LOCAL mode only', which is useful extra behavior not in annotations. However, it doesn't explain the implications of deleting in other modes or whether the action is reversible (though destructiveHint implies not). No contradictions with annotations.

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 a single short sentence with no filler words. It front-loads the action and appends the mode constraint. Every word adds value – it is appropriately concise for a simple tool.

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 simple delete tool with one parameter and annotations covering destructive/idempotent behavior, the description is mostly complete. However, the 'LOCAL mode only' parenthetical is ambiguous (tool availability vs. data scope), and nothing explains what happens if the reminder doesn't exist or how mode interacts with other tools. The absence of an output schema is acceptable, but the mode ambiguity leaves a gap.

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 covers the sole parameter reminderId with a description 'ID of the reminder to delete (required)'. The tool description adds no additional parameter details, such as how to obtain the ID or format. With 100% schema coverage, the baseline is 3, and the description doesn't exceed it.

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 uses a specific verb 'Deletes' and identifies the resource 'a reminder', making the core action unambiguous. The parenthetical 'LOCAL mode only' adds a scope constraint, though it could be clearer whether it refers to the tool's availability or the data type. It distinguishes from sibling tools like complete-reminder by the delete verb.

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 provides no guidance on when to use this tool versus alternatives like complete-reminder or update-reminder. The only usage hint is 'LOCAL mode only', which is a restriction but not a directive or comparison. No alternatives are named, and no prerequisites (e.g., checking mode via check-auth-status) are mentioned.

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