reschedule_reminder

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

The description discloses that it returns a structured JSON with the updated reminder or an error message, but lacks details on side effects, permissions, or what happens if the identifier matches multiple reminders. Since no annotations are provided, the description carries the burden but is only partially complete.

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 concise, front-loaded with the purpose, and uses a clear args/returns structure with no wasted words. 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 presence of an output schema and the tool's moderate complexity, the description covers basic functionality and return type but omits edge cases (e.g., non-unique identifier, rescheduling completed reminders). It is adequate but not comprehensive.

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?

With 0% schema coverage, the description adds significant meaning beyond the schema, explaining each parameter's role and format (e.g., 'identifier' can be id or name, 'datetime' format specified). This compensates well for the missing schema descriptions.

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 'reschedule' and the resource 'reminder', and specifies that it works for an exact or uniquely matching reminder. However, it does not explicitly distinguish itself from the sibling tool 'update_reminder', which likely serves a similar purpose.

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 provides no guidance on when to use this tool vs. alternatives such as 'update_reminder' or 'set_reminder'. It does not mention prerequisites or when not to use it, leaving the agent to infer usage context.

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