tasks_list

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

No annotations are provided, so the description must disclose behavioral traits. It only states the basic function and fails to mention default filtering behavior (e.g., show_completed defaults to false, meaning completed tasks are hidden) or any other operational details like pagination or ordering.

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 exceptionally concise, containing two sentences with no filler. It front-loads the core purpose and then provides the key usage tip about @default, demonstrating efficient communication.

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?

While an output schema exists, the description lacks important context such as the default task view (incomplete only) and how this tool relates to tasks_list_tasklists for discovering task list IDs. It is adequate for a simple list operation but leaves gaps for an agent to fully utilize the tool.

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?

With 0% schema description coverage, the description should compensate for all parameters. It only explains the special value '@default' for tasklist_id, leaving max_results and show_completed unexplained. The parameter names are somewhat self-evident, but the default behaviors are not clarified.

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 clearly states the tool lists tasks within a task list, using a specific verb and resource. It differentiates from siblings like tasks_list_tasklists by specifying 'tasks in a task list' rather than task lists themselves.

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 provides a usage hint for the primary list ('Use @default') but does not explicitly contrast with alternatives like tasks_list_tasklists. Usage context is implied through the description but exclusions and alternative selection guidance are missing.

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