list_reminders

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

With no annotations, the description carries the behavioral disclosure burden. It implies a read-only listing operation and names the ledger and statuses involved, but it does not state whether completed reminders are returned by default, how the limit affects results, or whether ordering/pagination is applied.

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 a single front-loaded sentence with no wasted language. It communicates the core action and scope efficiently.

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?

An output schema exists, so return values need not be explained. However, the description lacks annotations, has zero schema description coverage, and does not explain key invocation details such as default status behavior or how the limit is applied, leaving important gaps for an agent selecting and invoking the tool.

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 must compensate for both parameters. It gives possible status values (pending, snoozed, completed), which partially explains the status parameter, but it says nothing about the limit parameter, its default of 50, or any maximum.

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 states a specific verb and resource: 'List reminders' from the Remy Reminders ledger. It also names the status categories covered (pending, snoozed, completed), which makes the tool's scope clear. It does not explicitly distinguish itself from nearby siblings such as list_open_tasks or search_tasks.

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 gives no guidance on when to use this tool versus alternatives like list_open_tasks, search_tasks, task_stats, or the reminder mutation tools. It implies that it lists reminders, but an agent must infer the selection context without any explicit when-to-use or when-not-to-use rule.

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