tasks_tasks_list

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

Annotations already mark this as read-only, so the description adds value by disclosing the non-obvious default filtering behavior: hidden and assigned tasks are excluded unless showHidden/showAssigned are set. It does not mention pagination or ordering, but those are less critical for a safe read call.

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 sentences carry the essential operation and the two important default exclusions with no repetition or filler. The core action is front-loaded before the flag guidance.

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?

For a 12-parameter read-only tool, the description plus full schema coverage gives an agent the essential context: required tasklist, default filtering, and inclusion flags. It omits explicit pagination guidance beyond the schema's pageToken/maxResults descriptions, but that is a minor gap.

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 100%, so the baseline is 3. The description adds practical flag semantics ('set showHidden/showAssigned to include them') and reveals default-state meaning that the raw schema only implies, lifting it slightly above baseline.

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 states a specific operation, 'List tasks in a task list,' identifying both the verb and the resource scope. This distinguishes it from single-task retrieval (tasks_tasks_get) and tasklist-level operations without requiring the caller to inspect sibling names.

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 purpose sentence implies use for enumerating tasks in a task list, but no alternatives or exclusions are named. There is no explicit guidance on when to prefer this over tasks_tasks_get or tasks_tasklists_list.

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