delete_task

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

Annotations already indicate destructiveHint=true, but the description adds critical detail about subtasks being left orphaned, which is beyond the annotation. This informs the agent about the side effects, which is valuable for decision-making.

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 concise, two sentences, with the key behavioral trait (subtask handling) front-loaded. It is efficient, though it could be slightly more structured with an explicit note on idempotency, but it is not verbose.

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's complexity (delete operation with side effects), the description covers the essential behavior, and the schema covers parameters. However, it does not state what happens when the task has dependencies or if the etag is required for conditional deletes, but these are covered by the schema. The output is not specified, but since there is no output schema, it might be beneficial to mention the return value, but it's not critical.

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 coverage is 100%, so each parameter (uid, etag, list) has a description. The tool description does not add additional parameter-level meaning beyond what the schema provides, so the baseline of 3 is appropriate.

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 clearly states the tool deletes a task permanently, with a specific verb and resource. It also distinguishes itself from update_task and complete_task by emphasizing permanence and the specific behavior regarding subtasks.

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 to use this tool (when you want permanent deletion), but does not explicitly state when not to use it or mention alternatives like update_task for soft deletion. The sibling list provides context, but the description could explicitly warn against using it for reversible actions.

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