Update task

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

With no annotations, the description must disclose behavior but only states 'This operation writes to Asana,' which is generic. It does not explain whether unspecified fields are preserved, how null or empty strings affect fields, or any side effects beyond writing.

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 short and front-loaded, but the second sentence ('This operation writes to Asana.') is redundant with the first and does not earn its place. A more compact but informative phrasing would be an improvement.

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 14-parameter write operation with no annotations and low schema coverage, this description is severely incomplete. It omits behavioral nuances like partial updates, clear-field semantics, and the meaning of complex fields, making it inadequate for reliable tool invocation.

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 only 29%, and the description adds no parameter-level detail. It does not clarify ambiguous parameters like custom_fields, resource_subtype, approval_status, or the date fields, leaving agents with insufficient information for correct invocation.

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 identifies the operation as updating fields on an Asana task and notes it is a write operation. This distinguishes it from read-focused siblings like get_task and search_tasks, though it does not explicitly contrast with create_task.

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?

No guidance is provided on when to use this tool versus alternatives like create_task for new tasks or get_task for reading. There is no mention of prerequisites such as having the task GID.

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