list_reminders

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

No annotations are provided, so the description carries the burden. It usefully discloses that setting flagged/priority changes result ordering ('sorted most urgent first (priority, then due)') and the tri-state flag semantics, but says nothing about include_completed, defaults, or result limits.

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?

Three front-loaded sentences with no filler; the main purpose leads and the smart-view details follow. Slightly dense but each sentence adds distinct 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?

An output schema exists, so return values need not be described, and the read-only nature is implied. Still, for a 4-param tool at 0% schema coverage, the total silence on include_completed leaves an agent without enough to call it confidently.

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 0%, so the description must compensate. It documents list (name or id, empty = all), flagged (True/False/null), and priority enum values that the schema omits entirely, but leaves include_completed completely unexplained.

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 ('List reminders') plus scope ('in one list (name or id), or across all lists if empty'). An agent can distinguish it from siblings like search_reminders by the explicit filtering/listing semantics, though the contrast is implied rather than stated.

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?

Explains the default behavior (empty list = all lists) and that setting flagged/priority triggers urgency sorting, which is useful context for invoking it. However, it never names when to prefer this over search_reminders or list_reminder_lists, so routing is left to inference.

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