listAsanaTasks

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

With no annotations provided, the description carries the full burden. The verb 'Retrieves' indicates a read-only operation, but it does not disclose behaviors like pagination, response structure, or whether filters are optional. It adds some transparency but misses several behavioral details.

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?

A single sentence of 13 words that is front-loaded and free of fluff. Every word contributes to understanding the tool's core function.

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 simple list operation with complete schema documentation, the description is adequate but leaves gaps: it does not state the default behavior when no filters are provided, whether results are paginated, or what the return format looks like. No output schema exists, so the description could have provided more context.

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?

The input schema covers 100% of parameters with meaningful descriptions, so baseline is 3. The description mentions the three filter criteria (project, assignee, completion) which align with schema properties, but adds no extra semantic beyond the schema.

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 verb ('Retrieves'), the resource ('tasks from Asana'), and the filtering dimensions ('project, assignee, and completion status'). It distinguishes itself from single-task tools like readAsanaTask, though it does not explicitly differentiate from searchAsanaTasks.

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 explicit guidance on when to use this tool vs. alternatives. The description implies usage for filtered task lists, but it does not mention searchAsanaTasks or other siblings, nor does it provide any exclusion criteria.

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