list_reminders

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

The timezone disclosure (+08:00) is a useful behavioral detail not inferable from the name or schema. However, with no annotations and no mention of pagination, default completion filtering, or other behavioral traits, significant aspects remain undisclosed.

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 filler. The timezone note is compact and relevant, making it appropriately sized and structured.

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 is relatively simple and an output schema exists, so return values are covered. However, the description omits guidance on optional parameters and default behavior, which creates notable gaps for a list operation with no 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?

The description does not address any of the three parameters (limit, list_id, include_completed), and schema description coverage is 0%. The schema provides only names and defaults, so the agent must infer semantics, making the parameter meaning insufficiently clarified.

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 phrase 'List reminders' clearly identifies a read operation targeting reminder resources, and the plural form distinguishes it from get_reminder. However, it does not explicitly differentiate from sibling tools like list_reminder_lists, so it stops short of a top score.

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, nor does it mention the optional filtering parameters or default behavior. No exclusions or alternative tool references are provided.

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