list_asana_tasks

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so safety and idempotency are covered elsewhere. The description adds no behavior beyond that: it does not mention pagination, whether completed tasks are included by default, what auth is needed, or what the response looks like.

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?

It is a single front-loaded sentence with no wasted words. However, its brevity comes at the cost of under-specification: there is no structure that tells the agent about defaults, paging, or alternatives.

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?

With no output schema and half the parameters undocumented, the description should carry more weight than one sentence. It leaves the agent guessing about default task status, result limits, authentication behavior, and how this differs from search_asana_tasks.

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 50%; completed and project_gid are documented in the schema, but limit and api_key have no description anywhere. The description adds no meaning about those parameters, their defaults, or how filtering works, so it does not compensate for the coverage gap.

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 states a specific verb and resource ('List tasks') and scopes it to an Asana project. It is clear what the tool does, but it does not distinguish itself from the sibling search_asana_tasks, which appears to serve a similar listing/search purpose.

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 guidance on when to use this tool instead of search_asana_tasks, get_asana_task, or list_asana_projects. The agent must infer from the name alone that this is the bulk-listing variant, and no conditions, exclusions, or alternatives are named.

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