cancel_reminderCancel (delete) one reminder by its reminderId (ids come from list_reminders or create_reminder). The saved item itself is not touched. Reminders synced to Google Calendar cannot be cancelled here - the user manages those at mark-it.co or in Google Calendar.
| Name | Required | Description | Default |
|---|---|---|---|
| reminderId | Yes | The reminder to cancel (from list_reminders) |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already mark this as destructive and idempotent. The description adds important behavioral context beyond those annotations: it deletes only the reminder, not the underlying saved item, and it does not work for Google Calendar-synced reminders. This meaningfully informs the agent about side effects and boundary conditions.
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 compact and front-loaded: the primary action and parameter source appear first, then the scope boundary, then the Google Calendar exclusion. Every sentence carries distinct information, with no filler or repetition.
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 single-parameter destructive tool with no output schema, the description provides all necessary context: what it acts on, how to obtain the ID, what side effects occur, and the key limitation. Nothing critical is missing for an agent to invoke it correctly.
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 a single parameter, so the schema already documents reminderId. The description adds useful provenance by stating that IDs come from list_reminders or create_reminder, which helps the agent select valid inputs. This exceeds the baseline without being redundant.
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 action ('Cancel (delete) one reminder'), identifies the specific resource (a reminder identified by reminderId), and differentiates itself from related tools like list_reminders and create_reminder. It also clarifies what the tool does not affect, making its scope unambiguous.
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?
It explicitly tells the agent where to get valid reminder IDs (list_reminders or create_reminder), and it provides a clear exclusion: reminders synced to Google Calendar cannot be cancelled here and must be managed elsewhere. This gives both a clear when-to-use and when-not-to-use signal.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool targets a distinct action: saving, searching, fetching, listing categories, managing reminders, and sending feedback. There is no meaningful overlap or ambiguity between tool purposes.
Tool names are uniformly lowercase snake_case and mostly follow a verb_noun pattern like save_item, list_categories, cancel_reminder. The exceptions are fetch and search, which are single verbs without an explicit object, creating a minor inconsistency.
Eight tools is a well-scoped count for a personal library and reminder assistant. Each tool earns its place and covers a distinct user need without unnecessary redundancy.
The core workflow of saving, searching, fetching, and reminding is well covered. However, there is no way to delete or update a saved item, which is a notable lifecycle gap for a library tool.