list_task_lists

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

No annotations provided, so description carries full burden. It discloses the required read-only scope ('Requires the tasks.readonly OAuth scope') and implies the operation is safe. However, does not mention pagination behavior beyond schema fields.

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?

Four sentences, each adding value: purpose, usage flow, sibling differentiation, and auth requirement. Front-loaded with the action. No redundant information.

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 simplicity and presence of an output schema, this description covers all necessary context: what it does, why to use it, alternatives, and auth. Completes the picture for an AI agent to select and invoke correctly.

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%, baseline is 3. Description adds context for output but does not enhance parameter meanings beyond the schema descriptions. The mention of 'discover task_list_id' hints at output but not parameter usage.

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 'List the user's Google Tasks task lists' with a specific verb and resource. It distinguishes from siblings by mentioning 'list_tasks' and 'manage_task_list', making the tool's purpose unambiguous.

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?

Explicitly says 'Use this to discover task_list_id before calling list_tasks, get_task, or manage_task' and 'For modifying task lists themselves use manage_task_list', providing clear when-to-use and when-not-to guidance. Also mentions required OAuth scope.

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