Manage notifications

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

The description says the tool can 'remove task reminders', but annotations declare destructiveHint=false. Removing a reminder is a destructive operation, so the description contradicts the annotation. The description also fails to disclose side effects or whether removal is reversible.

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 one tight sentence with the core action words front-loaded and a compact parenthetical clarifying reminder modes. No words are wasted.

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?

Even with an output schema, the description is too sparse for a multi-action tool with six parameters and no required fields. It does not specify parameter combinations per action, the difference between task_id and task_name, or how list/add/remove are invoked, and the destructiveHint contradiction further undermines safe use.

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 only 33% (absolute_date and minutes_before_due), and the description only echoes the absolute/due-relative distinction. It does not explain how task_id, task_name, and notification_id relate to each action, nor which parameters are required for add versus remove. This leaves substantial ambiguity for a six-parameter tool.

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 states a clear verb set ('List, add, or remove') and a specific resource ('task reminders'), with the useful distinction of 'absolute or due-relative'. An agent can identify the tool's job and tell it apart from sibling tools like manage_tag or manage_perspective.

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 does not say when to use this tool over siblings such as query_tasks, add_task, or manage_perspective, and it gives no exclusions or prerequisites. The usage context is only implied by the tool's name and purpose.

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