Add Reminder

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

No annotations are provided, so the description must carry the burden of disclosing behavior. It only states 'Create a new reminder' and lists supported attributes, but does not mention success/failure behavior, permissions, default list handling, or what happens if a specified list does not exist. The description is minimal and lacks depth.

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 two concise sentences: the first identifies the action, the second summarizes capabilities. Every word is useful, and there is no redundancy or irrelevant detail.

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?

The tool has no output schema and no annotations, yet the description is only a basic overview. It does not clarify return values, default list behavior, error cases, or the interaction with sibling tools (e.g., whether the list must pre-exist). It is adequate for a simple create operation but leaves several gaps.

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 five parameters. The description's phrase 'list, due date, notes, and priority' merely echoes the schema without adding extra meaning or usage nuances.

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 explicitly states 'Create a new reminder in Apple Reminders,' using a specific verb and resource, and lists supported fields (list, due date, notes, priority). This clearly distinguishes it from sibling tools like edit-reminder, complete-reminders, and delete-reminders.

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 clearly indicates the tool is for creating new reminders, which sets it apart from siblings for editing, completing, or deleting reminders. However, it does not explicitly mention alternatives or state when not to use this tool.

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