reminders_create

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

The description only states 'Create a reminder', implying mutation, but provides no additional behavioral details. With no annotations, the description carries the full burden but fails to disclose potential side effects, required permissions, or what happens if the list does not exist.

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 with no wasted words. It is efficient, though the content is minimal.

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 5 parameters, no output schema, and no annotations, the description is incomplete. It does not mention return values, parameter relationships, or any prerequisites (e.g., list must exist). The minimal statement leaves much for the agent to infer.

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 20% (only 'due' has a description). The tool's description adds no meaning to any parameter—it does not explain what 'list' refers to, the role of 'name', 'notes', or 'priority', nor their constraints.

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 verb 'Create' and the resource 'a reminder' with the context 'in a list'. It is distinct from sibling tools like reminders_complete, reminders_delete, and reminders_list, which have different actions. No ambiguity.

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 guidance on when to use this tool versus alternatives. For example, it doesn't mention that reminders_list_lists should be used first to obtain a valid list identifier, or that reminders_search might be preferred for finding existing reminders.

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