List Reminders

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

Beyond the readOnlyHint annotation, the description adds critical behavioral details: it never auto-enumerates all reminders (prevents misuse), and explains the fallback behavior when no list is provided. The limit parameter's default and maximum are also specified.

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?

Extremely concise, with all essential information packed into a few sentences. The most critical constraints are front-loaded (list requirement, fallback behavior). No superfluous words.

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?

Covers the main behavior, required parameters, fallback, and limit. However, it omits explanation of the completed parameter. Since an output schema exists, return values need not be described, but the missing param is a gap. Still, overall completeness is good.

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 carries the full burden. It explains the purpose of list_name/reminders_list_id (required, but either is sufficient) and the limit parameter (default 20, max 100). However, the completed parameter is not mentioned, leaving its purpose unclear.

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?

Clearly states 'List reminders from a specific list.' This provides a specific verb (List) and resource (reminders) with the scope 'from a specific list.' It distinguishes itself from siblings like reminders_search (search across lists) and reminders_today (today's reminders) by focusing on a single list.

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?

Explicitly states that list_name or reminders_list_id is always required, and that omitting both returns available lists for the user to pick. It warns against enumerating all reminders across lists. While it doesn't name alternatives, it provides clear when-to-use context.

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