Permanently remove a reminder from an iCloud Reminders list by specifying its list name and reminder ID. Use dryRun to preview the deletion before making changes.
Delete a reminder from iCloud Reminders permanently.
| Name | Required | Description | Default |
|---|---|---|---|
| dryRun | No | If true, report exactly what would change and do not modify anything | |
| listName | Yes | List name containing the reminder | |
| reminderId | Yes | Reminder ID to delete |
Changes observed during successful MCP inspections.
v2.8.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the behavioral burden. It discloses the critical trait that deletion is permanent (irreversible), which is valuable. However, it omits other behavioral context such as dry-run interaction, failure behavior, or permission requirements.
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, front-loaded sentence that names the action and scope without any wasted words. It is appropriately sized for a simple delete 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 tool with full schema coverage and no output schema, the description is minimally sufficient to invoke correctly. However, it lacks sibling differentiation and usage context that would help an agent choose between deleting, completing, or updating a reminder.
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 100%, so the schema already documents all three parameters including dryRun. The description adds no additional parameter semantics, making the baseline 3 appropriate.
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 ('Delete') and resource ('a reminder from iCloud Reminders') plus an important scope qualifier ('permanently'). It does not explicitly differentiate from siblings such as complete_reminder or update_reminder, so it falls short of a 5.
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 explicit when-to-use, when-not-to-use, or alternative guidance. The description only states what the tool does; it does not help an agent choose it over complete_reminder, update_reminder, or bulk delete tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.