add-reminders

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

Annotations indicate a write operation (readOnlyHint=false) and non-destructive (destructiveHint=false). The description adds the three reminder types and taskId requirement, but does not disclose if reminders are appended or if duplicates are handled. The description is consistent with annotations, providing adequate but not rich behavioral context.

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?

Two concise sentences with no waste. Essential information is front-loaded, and every sentence adds value.

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 complex input schema with nested oneOf and the existence of an output schema, the description covers the core functionality. It could mention that multiple reminders can be added at once (max 25) and delivery methods, but these are in the schema. The description is sufficiently complete for a tool with rich schema.

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 coverage is 100%, with detailed descriptions for each property. The description mentions the three types and taskId requirement, which are already in the schema. It does not add new meaning beyond the schema, so baseline 3 is appropriate.

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 'Add reminders to tasks' with a specific verb and resource. It lists the three supported types (relative, absolute, location) and the requirement for a taskId, distinguishing it from siblings like update-reminders or find-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 implies usage for adding reminders but does not explicitly state when to use it versus alternatives (e.g., updating existing reminders with update-reminders) or prerequisites (e.g., task must exist). No exclusions or context are provided.

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