Create Reminder

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

Annotations already indicate this is a non-read, non-destructive operation. The description adds the important behavioral constraint that it operates only in LOCAL mode, which is not captured by annotations or schema. It does not disclose additional traits like side effects, return values, or failure behavior, so it only partially covers the burden.

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, front-loaded sentence that conveys the core purpose and a critical constraint with zero wasted words. It is appropriately sized for a simple create operation and achieves maximum conciseness.

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?

Given the tool's moderate complexity (5 params, all but one optional), the schema's thorough documentation, and the presence of annotations, the description is adequate but minimal. It states the action and mode restriction but omits any context about behavior, return value, or interplay with other tools. It is sufficient for a straightforward create action but leaves room for more proactive description.

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?

The input schema provides descriptions for 100% of parameters, so the baseline is 3. The description contributes no additional parameter information, but it does not need to compensate because the schema already fully documents each field. It neither enhances nor detracts from parameter understanding.

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 identifies the tool's action ('Creates') and resource ('a new reminder'), with an additional scope constraint ('LOCAL mode only'). It unambiguously distinguishes from sibling create tools like create-event and create-note by naming the specific resource type.

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 implies usage through its imperative verb and resource, and the 'LOCAL mode only' qualifier gives a conditional restriction, suggesting it should be used only in local mode. However, it does not explicitly name alternatives or provide when-not-to-use guidance beyond the mode constraint, so it falls short of a clearer guideline.

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