tasks.tasklists.delete

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

With no annotations, the description carries the full burden and does so: it discloses cascading deletion of assigned tasks and originals in Docs/Chat Spaces, irreversibility absent a trash/undo flow, refusal under --readonly safety profiles, and that the response is the post-delete resource state or empty. This is exactly the risk context an agent needs before a destructive call.

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 lead sentence is well front-loaded with the destructive cascade, but the trailing clauses about HTTP verb, readonly profiles, and body construction are crammed into a single dashed run-on that dilutes the core warning. It is informative but not tightly 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?

For an unannotated destructive tool with no output schema, the description covers consequences, reversibility, safety-profile behavior, and return value. Auth scopes and required permissions are the main omission.

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 the baseline is 3. The description adds only a note on how request bodies are assembled (typed flags beating the `params` map, `body_file` override) and nothing about the required `tasklist` identifier or `dry_run` semantics beyond what the schema already documents.

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 ('Deletes the authenticated user's specified task list') and explicitly enumerates the sibling operations over the same resource (get, insert, list, patch, update). An agent can distinguish delete from patch/update without opening any 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 implies when the tool is appropriate (irreversibility, refusal under --readonly, cascade to assigned tasks) but never states an explicit when-to-use vs. alternative, e.g. clearing tasks versus deleting the list. The sibling list names alternatives but doesn't route between them.

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