asana_bulk_update

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

Explicitly discloses the internal looping behavior (Loops PUT per task), failure handling (continues past individual failures), and return format (per-task summary). This goes significantly beyond annotations that only declare readOnly=false, idempotent=true, and destructive=false, providing essential execution semantics.

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 no filler, front-loading the defining characteristic ('SAME field changes') and packing in behavior, error handling, and output summary. Every word earns its place.

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?

The description covers the core calling pattern, failure behavior, and return summary, which is strong for a tool with no output schema. Missing only minor details like batch size limits or rate-limit implications, but overall an agent can invoke and interpret results correctly.

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% and the description merely lists the same parameter categories ('assignee, dates, completed, notes/html_notes, custom_fields') without adding meaning beyond what the schema already documents. It does not elaborate on the custom_fields structure or edge cases, so baseline 3 applies.

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 a specific verb ('Apply') and resource ('MANY tasks') with the key 'SAME field changes' qualifier, distinguishing it from per-task update tools. It lists the exact fields it can update, leaving no ambiguity about scope.

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 bulk use via 'MANY tasks in one call' but does not explicitly say when to prefer this over alternatives like asana_batch_update or asana_set_dates. No when-not-to-use guidance is provided, though the 'SAME field changes' constraint is a clear condition.

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