list_reminders

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

Annotations already provide readOnlyHint and openWorldHint. The description adds concrete behavioral details: default ordering, default filtering (incomplete only), pagination via limit/offset with total and truncated flag, and date format requirements. Minor omission: no mention of error handling or empty results.

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 extremely concise: two sentences plus parameter details. Every word adds value, with purpose front-loaded. No extraneous information.

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?

Given the presence of an output schema (total and truncated flag mentioned), the description covers key aspects: ordering, filtering, pagination, date formats. Minor gap: does not specify default limit value or explain behavior for duplicate due dates. Still adequate for a list tool with 6 parameters.

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?

With 0% schema description coverage, the description compensates by explaining the list parameter (accepts list_id or display name), due date parameters (ISO-8601), and pagination (limit/offset). However, the completed parameter is only indirectly described via 'Defaults to incomplete only' and limit's default value is not restated.

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 tool lists reminders and specifies ordering (earliest-due first, undated last) and default filtering (incomplete only). It distinguishes from sibling tools like get_reminder (single reminder) and list_lists (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?

The description implies this tool is for listing multiple reminders but does not explicitly state when to use it versus alternatives like get_reminder or list_lists. No when-not or alternative tool mentions are provided.

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