Create Reminder

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

Annotations only include a title, providing no behavioral hints. The description 'Create a reminder.' gives no additional behavioral context beyond the obvious creation action. It does not disclose side effects, required permissions, or any other behavioral traits, leaving the agent with insufficient transparency.

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 extremely short but this conciseness comes at the cost of useful information. It essentially repeats the tool name, making it under-specified rather than efficiently informative. The sentence does not earn its place as it adds no value beyond the title.

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 has 6 parameters (many optional) and an output schema, the description is grossly incomplete. It lacks parameter explanations, usage context, and behavioral details. The agent cannot use this tool effectively without additional information from elsewhere.

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 0%, meaning the input schema provides no parameter descriptions. The description adds no explanation of parameters like 'due', 'notes', 'priority', 'list_name', or 'reminders_list_id'. While parameter names are somewhat self-explanatory, the lack of any semantic guidance forces the agent to guess, reducing effectiveness.

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 'Create a reminder.' clearly identifies the verb and resource, but lacks any differentiation from sibling tools like 'reminders_create_list' or 'reminders_update'. It does not specify scope or distinguish between creating a reminder item versus a reminder list.

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?

No usage guidelines are provided. The description does not indicate when to use this tool versus alternatives such as 'reminders_create_list', 'reminders_update', or other reminder tools. There is no context on prerequisites or typical use cases.

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