List reminders

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

Annotations already signal this is read-only; the description adds the useful sort-order and optional-filter behavior. It does not mention that status can override 'upcoming' with done/cancelled/all, but the schema covers status values and default.

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?

One focused sentence that front-loads the core behavior and then lists the optional filters. Every phrase earns its place with no redundancy.

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 read-only list with a fully documented schema and an output schema, the description plus schema is sufficient. The only minor gap is that 'upcoming' is not reconciled with statuses like done/cancelled, though the schema disambiguates.

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 100%, so the schema fully documents member, status, and within_hours. The description only restates their existence at a high level, adding no new meaning 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?

Uses a specific verb and resource ('Lists upcoming reminders') plus a sort-order detail ('soonest first') that distinguishes it from other list_* siblings. It is immediately clear which family of objects this tool reads.

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 the tool is for fetching reminders, but it never states when to prefer it over similar read/list tools or what it is not for. No exclusions or alternative routing are provided, so the agent must rely on the tool name.

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