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

Annotations already flag destructiveHint=true, but they don't say what the destruction covers or whether it is reversible. The description supplies both: the entire task list contents are removed, and there is no recycle bin, so the operation is irreversible. It stops short of disclosing permission or auth requirements, so it earns 4 rather than 5.

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?

Two short sentences with zero filler; the destructive scope lands first and the irreversibility warning follows immediately. Nothing is redundant with the title.

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 destructive mutation with no output schema, the description covers the two things an agent most needs: what is destroyed (the whole list) and that it cannot be undone, plus a confirmation requirement. The remaining gap is how to obtain a valid listId, which is left entirely to the undocumented parameter.

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 only 50%: mailbox is documented in the schema (including a pointer to list_authorized_mailboxes), but listId carries no description at all. The description adds nothing about parameters – notably it never tells the agent where listId comes from (list_google_task_lists) – so it fails to compensate for the coverage gap.

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?

States a specific verb and resource ('Delete a task list') and goes further by naming the cascade scope ('and every task in it'), which cleanly separates it from delete_google_task and delete_outlook_task_list. An agent can route correctly without opening the schema.

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 gives a real usage constraint – 'ask the user to confirm first' – which is actionable behavioral guidance. However, it never states when to prefer this over siblings (e.g. delete_google_task for a single task, or emptying a list instead of deleting it), so the routing guidance is only implied.

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