list_tasks

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

With no annotations provided, the description carries the full burden. It discloses key behaviors: completed tasks are excluded by default, and summary vs. verbose output is toggled via verbose. However, it omits other behaviors such as pagination, sorting, filter combination logic, or permission requirements, leaving gaps.

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?

The description is three sentences, front-loaded with the main purpose, followed by concise behavior notes on defaults. Every sentence contributes value, with no wasted words.

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?

With 9 parameters, no output schema, and no annotations, this description is under-specified. It provides high-level defaults but no details on return shape, filter interactions, pagination, or edge cases, making it incomplete for a tool of this complexity.

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?

The schema has 9 parameters with 0% description coverage, so the description must compensate. It only explains includeCompleted and verbose, leaving tags, status, assignee, dueAfter, dueBefore, priority, and projectId undefined. This is insufficient for an agent to use the tool correctly.

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 tasks' and clearly identifies the resource (tasks) with optional filters. It distinguishes from sibling tools like get_task (single task retrieval) by focusing on listing multiple 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 gives clear context on default behavior (excludes completed tasks) and how to opt in (includeCompleted=true), but does not explicitly compare with alternatives like get_task or get_tasks_by_tag. There is no when-not-to-use guidance, leaving tool selection partially implied.

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