asana_delete_task

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

Annotations already declare destructiveHint=true and idempotentHint=true. The description adds valuable nuance beyond annotations: the specific confirmation gate, the no-op behavior without confirm, and the permanence of the deletion. No contradiction with annotations.

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 sentences with zero wasted content. The destructive warning is front-loaded, the confirmation requirement is explicit, and the consequence of a false confirm is stated.

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 simple delete with two fully-schema'd parameters and annotations covering destructive/idempotent behavior, the description provides all needed operational detail: the confirmation gate, the no-op consequence, and permanence. Nothing essential is missing.

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 both parameters are already well described in the schema. The description adds semantic clarity for the 'confirm' parameter (that it gates the operation and produces a no-op report), but this is marginal beyond an already excellent schema.

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?

Description states a specific verb ('delete') and resource ('task'), clearly naming it as a permanent (trash) deletion. It is unambiguous and distinguishes itself from mutation tools like asana_update_project and asana_set_dates.

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?

Description provides explicit context on when it takes effect: 'Requires confirm:true (C13 gate)' and when it does not ('Without confirm it is a no-op'). It does not name alternative deletion tools (e.g., asana_delete_project), but the action is specific enough that selection is unambiguous.

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