tasks.tasks.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 declares the operation irreversible (absent a trash/undo flow), notes it is refused under --readonly safety profiles, states it maps to HTTP DELETE, and describes the post-delete response as JSON.

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 destructive behavior and assignment caveat are front-loaded, but the trailing generic template text about request bodies and body_file is irrelevant boilerplate for a bodyless DELETE and dilutes the message.

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 six-parameter destructive tool with no annotations and no output schema, the description supplies the safety profile, irreversibility, HTTP method, and return-value description — everything an agent needs to decide and call 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?

Schema description coverage is 100%, so task, tasklist, query, params, dry_run, and body_file are already documented. The description restates the precedence rule (typed flags win over the params map) and body_file, adding no new parameter meaning, which matches the baseline 3 when the schema does the work.

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?

Opens with a specific verb+resource ("Deletes the specified task from the task list") and adds a genuinely distinguishing nuance: deleting an assigned task also removes the original in Docs/Chat Spaces. It lists sibling tools by name but never contrasts them, so it stops short of full sibling differentiation.

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?

Provides an explicit alternative path with a condition: to delete only the assignment, go to the assignment surface and unassign instead. It gives no guidance, however, on when to use this versus tasks.tasks.clear or tasks.tasks.update.

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