asana_delete_task

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

With no annotations, the description carries the full behavioral burden, and it does deliver the single most important trait: permanent, irreversible deletion. It remains silent on other consequential behaviors an agent would want before calling it — whether subtasks, stories, or tag associations are cascade-deleted, what permissions are required, and what the response contains.

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 core action is front-loaded and the destructive warning follows immediately. Nothing could be removed without losing information.

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, irreversible operation with no annotations and no output schema, the definition covers the essential warning but omits cascade effects, permission prerequisites, and error behavior. An agent can call it correctly, but cannot fully predict the consequences of doing so.

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?

Only one parameter exists and the schema documents it fully ('The task ID to delete'), so the schema already carries the semantics. The description adds nothing about the ID's format or accepted sources (GID vs. name), making this a baseline case where the schema does the heavy lifting.

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'), which cleanly distinguishes it from the many read/create/update siblings sharing the asana_ prefix. It does not, however, explicitly differentiate itself from other delete siblings such as asana_delete_tag or asana_delete_project_status beyond the resource noun.

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?

There is no guidance on when to use this versus alternatives (e.g. removing a task from a project with asana_remove_project_from_task instead of deleting it outright) and no stated prerequisites or permission requirements. The irreversibility note hints at caution but is not framed as usage guidance.

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