google_tasks_list_tasks

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

With no annotations, the description must carry the full burden of behavioral disclosure. It only states 'List tasks' without any detail about read-only nature, pagination via maxResults, default behavior, or what the response contains. This is insufficient for an agent to understand the tool's effects.

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, which is concise but too terse for a tool with 4 parameters and no output schema. It states the purpose but omits critical information. It is not verbose, but it is under-specified rather than efficiently structured.

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 has 4 parameters (none described), no annotations, and no output schema, the description is extremely incomplete. It fails to explain how to use the tool, what parameters do, or what the return value looks like, leaving the agent with insufficient context to invoke the tool 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?

The input schema has 4 parameters with 0% description coverage, meaning no parameter descriptions exist. The tool description does not mention any parameter or provide any additional meaning, failing to compensate for the schema gap. The agent receives no context for maxResults, showHidden, tasklistId, or showCompleted.

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 Google Task list' uses a specific verb ('list') and clearly identifies the resource ('tasks in a Google Task list'). It effectively distinguishes this tool from siblings like 'google_tasks_create_task' or 'google_tasks_list_tasklists'.

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 guidance is provided on when to use this tool versus alternatives. It does not mention prerequisites (e.g., needing a tasklist ID from list_tasklists), nor does it explain when to use parameters like showHidden or showCompleted to filter results.

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