updateAsanaTask

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

No annotations are provided, so the description carries the burden. It indicates a mutation ('Updates') and lists fields, suggesting partial updates ("with new values"). However, it does not disclose whether updates are partial or full, why custom_fields is required, error handling, or return behavior. The schema descriptions fill some gaps, but the description adds limited behavioral context.

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 a single, concise sentence that front-loads the action and resource. It lists fields efficiently without fluff, making it appropriate in length.

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 7 parameters, 2 required, and no output schema, the description is minimal. It covers the core purpose but does not explain required custom_fields behavior, return values, or failure modes. Adequate but with clear gaps for a tool of this complexity.

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 the baseline is 3. The description merely restates the field names without adding additional meaning beyond what the schema already provides (e.g., date format, assignee special values). No extra semantic value is added.

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's purpose: 'Updates an existing Asana task' with a specific list of updatable fields (name, notes, due date, assignee, completion status, custom fields). This distinguishes it from sibling tools like createAsanaTask (which creates) and readAsanaTask (which reads).

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 use when modifying an existing task, but does not explicitly state when to use or not use alternatives. It lacks exclusions or explicit comparisons to sibling tools like createAsanaTask, leaving usage context implicit.

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