list_reminders

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

No annotations provided, so description must cover behavior. It clarifies that only uncompleted reminders are listed and explains parameter effects. However, it does not disclose rate limits, authentication needs, or return format details beyond mentioning ids.

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 with two paragraphs and a parameter list. The purpose is front-loaded, and every sentence serves a clear purpose. No fluff.

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?

For a simple list tool with 3 optional params, the description covers use case and parameter semantics well. It lacks explicit output schema info, but mentions returning ids and uncompleted reminders. Could improve by stating that no output schema is provided.

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%, so the description fully explains parameters: date formats, example values, conditions for use (e.g., include_undated only when start/end given). This adds significant value beyond the schema.

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 lists uncompleted reminders for viewing, modifying, deleting, or completing. It explicitly distinguishes from siblings by focusing on uncompleted reminders and includes id retrieval.

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 says when to use (before viewing/modifying/deleting/completing) and when to use time range filtering. It implies not for completed reminders, but does not explicitly name list_completed_reminders as alternative.

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