tasks_list

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

With no annotations, the description carries the full burden of transparency. It only mentions the output payload and does not disclose behavioral details such as pagination (page parameter), ordering (order_by, reverse), whether closed tasks are included, or subtask handling. The read-only nature is implied but not stated.

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, front-loaded sentence: 'Get tasks from a ClickUp list. Returns task details including name, description, assignees, and status.' Every word contributes to the core meaning, and there is no redundancy or filler.

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 six parameters and no output schema, the description is inadequate. It does not explain how the parameters (page, reverse, order_by, subtasks, include_closed) affect the behavior or results, nor does it describe the response structure beyond a superficial list of fields. A more complete description would cover pagination, filtering, and output format.

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 input schema already describes all six parameters with 100% coverage, so the description adds no extra parameter semantics beyond that baseline. The schema's descriptions are sufficient, and the description does not need to repeat them.

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 action ('Get tasks') and resource ('ClickUp list'), and lists the returned fields (name, description, assignees, status), which distinguishes it from sibling tools like tasks_get (which likely fetches a single task) or tasks_create.

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 no guidance on when to use this tool versus alternatives such as tasks_get, tasks_create, or tasks_update. There is no mention of typical use cases, prerequisites, or exclusions, leaving the agent to infer usage solely from the tool name.

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