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

No annotations are provided, so the description carries the full burden. It only states 'Create a new task list' with no information about side effects, permissions, idempotency, or what the tool returns. For a mutation tool, this is a significant gap.

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 one short sentence, which is front-loaded and concise, but it is under-specified. It does not waste words, but it omits essential context that an agent needs. It is not verbose, but it is not appropriately sized for the information it should convey.

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 only two parameters and no output schema, a minimal description might be acceptable, but the description fails to explain what a task list is, what the tool returns (e.g., the list ID), or how it differs from similar tools. The presence of many sibling tools makes this lack of differentiation problematic.

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 schema describes only the mailbox parameter (50% coverage). The description does not explain the title parameter or its purpose, nor does it add any additional meaning to either parameter. The agent must guess that title is the name of the list, which is not stated.

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 clear verb ('Create') and resource ('task list'), and the tool name clarifies it's for Google Tasks. It distinguishes from create_google_task (which creates a task, not a list), but it does not explicitly mention Google in the description itself, relying on the name. It is clear and unambiguous enough for an agent to know the intended action.

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 its siblings like create_google_task or create_outlook_task_list. There is no mention of context, prerequisites, or alternatives. An agent is left to infer usage from the name and schema.

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