Create task list

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

With no annotations, the description carries the full disclosure burden and says nothing beyond the bare action. It does not say whether the list becomes the default, what identifier comes back, whether account must pre-exist, or any mutation side 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?

A single efficient sentence with the action front-loaded and no filler. It is appropriately sized for a simple create call, though it is arguably too terse to be fully useful.

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 two-parameter create with no annotations and no output schema, the definition is minimally sufficient – the agent knows what it creates from the name and schema. It omits the return value (e.g., the new list's ID) and the account-default behavior, which the missing output schema leaves unexplained.

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 description coverage is 100%, so both parameters (title, account) are already documented in the schema; baseline 3 applies. The description adds no extra meaning such as how 'account' resolves to a nickname or what happens if omitted.

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 gives a specific verb (Create) and resource (Google Tasks list), and 'new' distinguishes it from update_list/delete_list siblings. It doesn't explicitly name alternatives, but the create semantics are 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?

No guidance on when to use this versus google_tasks_update_list, google_tasks_list_lists, or the more generic google_tasks_create. No mention of prerequisites such as which account is needed or whether one must exist first.

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