Find open tasks past their due date, sorted by most overdue first, for the whole account or a single project.
List open tasks whose due date has passed, most overdue first.
| Name | Required | Description | Default |
|---|---|---|---|
| project_id | No | Limit to one project; omit for the whole account. |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden. It states the filter and ordering but does not explicitly state side-effect-free behavior or return format. However, 'List' implies read-only, and the description is not misleading. It adds some behavioral detail (open, overdue, sorted) beyond the name.
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?
A single, information-dense sentence with no filler. The key constraints are front-loaded.
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?
For a simple list tool with one optional param and no output schema, the description is adequate. It doesn't explain the response format, but that is not required. It might benefit from noting it returns only open tasks, but it already does. It is complete enough for an agent to call it correctly.
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 100%, so the parameter project_id is already described. The tool description doesn't add param-specific details, but that's acceptable given the schema's high coverage. Baseline 3 applies.
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 uses a specific verb 'List' and a specific resource 'open tasks' with a clear condition (due date passed) and ordering (most overdue first). It clearly distinguishes from siblings like get_tasks or search_tasks by focusing on overdue and open tasks.
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 when to use it (when you need overdue tasks) but does not explicitly mention alternatives or exclusions. It provides clear context for its intended use.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.