Remove calendar events from OurFamilyWizard by event ID. For repeating events, choose whether to delete future occurrences as well.
Delete an OurFamilyWizard calendar event
| Name | Required | Description | Default |
|---|---|---|---|
| eventId | Yes | Event id — the `id` from ofw_list_events / eventRecurrenceId from ofw_create_event | |
| includeFuture | No | For repeating events: also delete future occurrences (default false) |
Changes observed during successful MCP inspections.
v2.8.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The annotation already indicates destructiveHint=true, so the description's 'Delete' is consistent but adds no new behavioral context (e.g., permanence, cascading effects on recurring events). It meets the minimum bar but does not exceed it.
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 sentence with no wasted words. It is appropriately front-loaded and easy to parse quickly.
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 no output schema, the description is mostly complete. However, it could briefly note that the action is irreversible or that includeFuture affects recurring events, which would improve completeness.
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?
Both parameters are fully described in the input schema (100% coverage). The description adds no additional meaning beyond the schema, so the score is baseline 3.
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 clearly states the verb 'Delete' and the resource 'OurFamilyWizard calendar event'. It is distinct from sibling tools like ofw_create_event and ofw_update_event, making it easy for an agent to select this tool when deletion is needed.
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, such as ofw_update_event for modifications. It does not mention prerequisites or conditions under which deletion should not be performed.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.