reminders_add

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

No annotations are provided, so the description carries the full burden. It only says 'Create a reminder,' which implies a write operation but provides no details on mutability, side effects, idempotency, or required permissions. Critical behavioral context is missing.

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 concise at three words, which is efficient but at the cost of missing essential details. It earns its place for brevity but should be longer to add value. A score of 3 reflects adequate brevity with incomplete substance.

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 five parameters, two required, and an output schema (details not shown), the description is woefully incomplete. It does not explain the return value, behavior on success/failure, or constraints on the recurrence parameter. The agent cannot reliably use this tool based on the description alone.

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 description must explain parameter meaning, but it does not. The description 'Create a reminder' adds no information about the 'text', 'time', 'recurrence', 'team_id', or 'user' parameters. The agent is left to infer from parameter names alone, which is insufficient.

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 tool creates a reminder, which is a specific verb+resource. However, it does not differentiate from other reminder-related sibling tools like reminders_complete or reminders_list, though the name 'reminders_add' is self-explanatory. The lack of sibling differentiation keeps it from a 5.

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. There is no mention of prerequisites, context (e.g., user authentication), or scenarios where this tool is appropriate. The description is too sparse to help an agent decide when to invoke it.

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