asana_my_tasks

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

Annotations already declare readOnlyHint=true and idempotentHint=true, but the description adds crucial behavioral context: the token-owner restriction, the 403 failure mode, and pagination behavior. This goes beyond what annotations provide and helps the agent predict outcomes accurately.

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 dense with essential information in a compact form: the purpose, the critical limitation, the alternative tools, and the pagination behavior. Every sentence contributes meaning 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 read-only list tool, the description covers the necessary context: what it lists, who can call it, failure mode, pagination, and alternatives. All parameters are well-documented in the schema, and no output schema is needed for a list endpoint. Nothing critical is missing.

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%, so the baseline is 3. The description adds value by clarifying the semantics of the 'user' parameter ('default me = token owner') and warning that passing another user fails with 403, which is not evident from the schema alone.

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 the TOKEN OWNER's My Tasks', identifying the specific resource and its scope. It also distinguishes this from other task-listing tools by emphasizing the personal PAT limitation, so an agent can tell it apart from asana_search_tasks or asana_list_tasks.

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 explicitly says when to use this tool (only for token owner's My Tasks) and exactly when not to, providing alternatives: 'For other users use asana_search_tasks or asana_list_tasks with assignee=<gid>'. It also warns about the 403 error, leaving no ambiguity.

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