List Reminders

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

Annotations already declare readOnlyHint=true and idempotentHint=true, covering safety and repeatability. The description adds the 'LOCAL mode only' trait, which is beyond annotations and provides useful behavioral context. It does not disclose other behaviors like pagination or ordering, but given the annotations, the additional context is sufficient.

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, concise sentence that communicates core functionality and constraints without wasting words. It is front-loaded and easy to parse.

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?

The tool has no required parameters, a fully descriptive schema, and an output schema. The description covers the main purpose and the critical mode restriction. Return values are handled by the output schema, so no additional detail is needed. This is complete for a simple list tool with strong annotations.

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 covers all parameters with descriptions (100% coverage), so the schema already handles parameter semantics. The description's mention of 'specific list or all lists' aligns with the listName parameter but adds no new meaning beyond the schema. Baseline of 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 the action ('Lists'), the resource ('reminders'), and the scope ('from a specific list or all lists'). It also includes the mode restriction ('LOCAL mode only'), which adds specificity and differentiates this tool from other reminder tools like 'search-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 retrieving reminders but provides no explicit guidance on when to choose this over alternatives such as 'search-reminders'. The 'LOCAL mode only' constraint is a clear exclusion for non-local modes, but no alternative tools are named.

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