tasks_list_tasks

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

No annotations provided, so the description carries full burden. It only states the basic purpose without disclosing behaviors like pagination, default filter (completed tasks excluded), or authentication requirements. This minimal disclosure is insufficient for a tool that returns data.

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 a single sentence of six words, very concise. However, it could include brief context on parameters or return value without significant bloat, so it slightly loses points for being too brief.

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?

Given no output schema and a simple list operation, the description is minimally adequate. It correctly identifies the tool's purpose but does not explain what the return value contains or how to handle pagination. Sibling tools exist but the description does not provide comparative context.

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 description coverage is 100%, and both parameters have clear descriptions (taskListId with default, showCompleted boolean). The tool description adds no extra meaning beyond the schema, so it meets the baseline expectation but does not enhance understanding.

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 'List tasks in a specific task list' clearly states the verb ('List'), resource ('tasks'), and scope ('in a specific task list'), effectively distinguishing it from siblings like tasks_list (which lists task lists) and tasks_get (gets a single task).

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?

No explicit guidance on when to use this tool versus alternatives like tasks_create or tasks_complete. The usage is implied (to get a list of tasks from a given list), but the description lacks context on when this is appropriate or when other tools would be better.

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