reminders_list_tasks

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered structurally. The description adds two useful facts beyond that: results are bounded (limit-capped at 500 per schema) and the tool requires the 'reminders' permission, which helps the agent anticipate auth gating.

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?

One front-loaded sentence covering action, filters, and result bound, plus a compact bracketed metadata tag. Nothing is padded, though the semicolon-joined metadata is slightly harder to parse than plain prose.

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?

An output schema exists, so return-shape explanation isn't required, and the annotations cover the read-only safety profile. The remaining gap is default behavior when filters and limit are omitted, but for a low-complexity 3-optional-param list tool the definition is largely sufficient.

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 only 33% (limit and completed have empty descriptions), so the description must compensate. It partially does by naming 'list' and 'completion' filtering, but says nothing about the limit parameter's default, upper bound, or what 'bounded result' means in practice when no limit is supplied.

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?

States a specific verb and resource ('Read reminders') and names the available filters (list, completion). It is clear what the tool returns, but it doesn't explicitly separate itself from the adjacent reminders_list_lists sibling, leaving the agent to infer the task-vs-list distinction from the name alone.

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 phrase 'optionally filtering list and completion' implies the intended use case (browse reminders with optional filters), but there is no explicit when-to-use statement, no when-not, and no pointer to reminders_list_lists or the create/update/complete siblings.

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