Get Multiple Tasks By Gid

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint. The description adds the 25-task limit and notes that it returns the same fields as asana_get_task, providing useful behavioral context beyond what the annotations convey.

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 three sentences, front-loaded with the core action, followed by efficiency and use case. Every sentence adds value with no redundancy or filler.

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 batch read operation, the description covers the key aspects: limit (up to 25), efficiency benefit, appropriate use case, and return field equivalence. It could mention error handling for invalid GIDs, but given the annotations and schema, it is sufficiently complete for an agent to select and invoke the tool.

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%, with detailed descriptions for both task_ids and opt_fields. The description does not add further parameter-specific detail beyond referencing task GIDs and the fact that return fields match asana_get_task, so the baseline 3 is appropriate.

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 explicitly states 'Fetch up to 25 tasks by GID in a single call', clearly identifying the verb (fetch), resource (tasks), and scope (by GID, up to 25). It also distinguishes itself from the sibling tool asana_get_task by positioning itself as a batch alternative.

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?

It provides clear usage guidance: 'Use when you have a known list of task GIDs (e.g. from a search result)' and explicitly compares to asana_get_task ('More efficient than calling asana_get_task repeatedly'). It does not explicitly state when not to use, but the context is strong enough to guide an agent.

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