list_due

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

No annotations are provided, so the description carries the full disclosure burden. It usefully reveals that only open tasks are returned and that the default window is end of this week, but it says nothing about ordering, inclusion of overdue items, pagination, or how limit truncation behaves.

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?

Front-loaded with the core semantics in the first line, followed by a compact Args block; no filler sentences. Slightly terse but every line earns its place.

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. For a two-parameter filter tool the description is adequate, but it leaves ordering, overdue handling, and the limit default unstated, which are the details an agent would still need.

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 description coverage is 0%, so the description must compensate, and it largely does: it supplies the accepted value grammar for 'by' (YYYY-MM-DD plus relative keywords today/tomorrow/week/next-week/month) and explains 'limit' as the maximum number of tasks returned. It is missing only the default value for 'limit'.

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 states a specific verb (list) plus resource (open tasks) and the exact filter applied (Due date on or before a given day), which an agent can act on directly. It does not, however, distinguish itself from the sibling list_today, which overlaps heavily when by=today.

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?

Usage is only implied: the 'on or before a day' phrasing tells the agent this is a deadline-window query, but there is no explicit statement of when to prefer it over list_today, search_tasks, or list_inbox, nor any exclusion conditions.

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