asana_list_tasks

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

No annotations are provided, so the description must fully disclose behavior. It reveals filtering behavior but does not mention pagination (though schema includes limit/offset), rate limits, authentication requirements, or that it is a read-only operation.

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 wasted words. The key filtering options and a valuable tip are front-loaded.

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?

Covers main filtering use cases but omits default behavior (e.g., what if no filters are provided?), sorting, and response structure. Without an output schema, some additional context would be beneficial.

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 description adds meaningful guidance beyond the schema descriptions, such as the workspace+assignee combination, project/section filtering, and the completed_since='now' trick. With 89% schema coverage, this elevates parameter understanding.

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 action (list tasks) and the main filtering options (workspace+assignee, project, or section). It distinguishes from siblings like asana_get_task (single task) and asana_list_task_comments (comments).

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?

Provides a specific guideline: use completed_since='now' for incomplete tasks only. However, it does not explicitly state when not to use this tool or differentiate from sibling tools like asana_list_tasks_in_section.

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