list_tasks

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

No annotations are provided, so the description carries the full burden. It implies a read-only listing and explains filtering semantics, but is silent on the two boolean flags that materially change results (show_completed, only_created_by_claude) and on how `limit` truncates output.

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 compact sentences, front-loaded with the core action and then parameter semantics, with no filler or restatement of the name.

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 value explanation is not required, and the filtering trio is well covered. But for a 6-parameter tool with zero schema descriptions and no annotations, three undocumented parameters (including both booleans that shape results) leave the agent guessing.

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 is the only documentation. It usefully clarifies that `tasklist` accepts an id OR a title and that `due_before` is inclusive and YYYY-MM-DD, but leaves `limit`, `show_completed`, and `only_created_by_claude` entirely undefined.

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+resource ('List tasks') and scopes it to one list, which separates it from write siblings like create_task and update_task. It does not explicitly distinguish itself from list_task_lists, but the resource noun (tasks vs. lists) does most of that work.

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 by the read/list framing and the note that the default list is used when `tasklist` is omitted. There is no explicit when-to-use or when-not-to-use guidance, and no mention of when filtering by query/due_before is preferred over fetching and filtering downstream.

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