tasks_list_tasklists

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

With no annotations, the description carries the full burden. 'List all' clearly indicates a read-only operation with no side effects, and 'all' discloses the scope. While it doesn't mention pagination or edge cases, for a simple no-parameter list tool the behavior is transparent enough.

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 short sentence that immediately states the action and resource. No wasted words, front-loaded, and easy to parse.

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 the tool's low complexity (no parameters), the presence of an output schema, and the clarity of the description, it is complete enough for an agent to select and invoke correctly. The description fully covers what the tool does.

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 tool has zero parameters, and the input schema is an empty object. The description adds no parameter details because none are needed. The baseline score of 4 applies for a tool with no parameters.

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 all Google Tasks task lists' uses a specific verb ('List'), identifies the resource ('Google Tasks task lists'), and specifies scope ('all'). This clearly distinguishes it from sibling tools like tasks_list (which lists tasks within a list) and tasks_create_tasklist (which creates a list).

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. It does not mention that tasks_list is for tasks within a list, nor does it describe exclusions or prerequisites. There is no explicit context beyond the basic purpose.

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