reminders_list

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

Without annotations, the description should disclose read behavior, but it only says 'list'. No mention of auth needs, rate limits, or other behavioral traits.

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?

Very concise, one sentence with no fluff. Could be expanded to include more details without losing conciseness.

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?

Lacks details on return format, pagination, sorting, or any special behavior. For a tool with no output schema and no annotations, more description is needed to ensure correct invocation.

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 coverage is 50%, but description only adds 'with optional filters', not specifying which parameters or their meaning. The schema describes due_after and due_before as ISO 8601, but list and completed lack schema descriptions. Description adds no new insight.

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?

Description clearly states the tool lists reminders in a specific list with optional filters. Verb 'list' and resource 'reminders' are explicit, and the requirement for a list is indicated, distinguishing it from search across lists.

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?

No guidance on when to use this tool versus siblings like reminders_search or when not to use it. No mention of alternatives or context.

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