list_tasks

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

With no annotations, the description carries the full burden of behavioral disclosure. It usefully reveals that omitting listId aggregates across all lists and that pagination is involved, but it does not describe auth requirements, ordering, return shape, or how includeCompleted affects results.

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?

Two brief sentences carry the essential scoping and pagination behavior with no filler. The instruction is front-loaded and immediately actionable.

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 description covers the main listId/pagination behavior but lacks guidance for choosing this tool over search_tasks, and with no output schema it does not clarify expected return fields. Given multiple siblings and four parameters, this is adequate but not complete.

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 75%, so the schema already documents most parameters. The description adds meaningful context for listId ('one list' vs 'page across every list'), but it does not add semantic detail for cursor, provider, or includeCompleted beyond what the schema already says.

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 verb 'List' and resource 'tasks' are clear, and the description adds specific scope behavior ('listId for one list; omit it to page across every list'). However, it does not explicitly differentiate from the sibling search_tasks, which also retrieves tasks in a filtered way.

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 a direct usage instruction for the listId parameter and when to omit it. It does not, however, state when to use this tool versus search_tasks or other task-related siblings, leaving the choice partially implicit.

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