listAsanaFavorites

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

No annotations are present, but the description carries the safety burden by using 'Retrieves' to indicate a read-only operation and by noting the authenticated-user and all-workspace scope. It does not mention pagination or empty-result behavior, which is a minor gap for a simple list endpoint.

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?

One tightly worded sentence gets straight to the point: the action, the resource, and the scope. No filler, front-loaded with the verb and object.

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 parameterless retrieval tool with no output schema, the description adequately explains what is returned (a list of favorite projects/tasks), the scope (all workspaces), and the auth context. It does not detail item structure, but that is acceptable given its simplicity.

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 has zero parameters, so the description has nothing to add beyond the schema. With 100% coverage and no params, baseline 4 applies.

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 uses a specific verb ('Retrieves a list') and resource ('favorite projects and tasks ... from Asana'), with a clear scope ('all workspaces' and 'authenticated user'). This clearly differentiates it from sibling tools like listAsanaProjects and listAsanaTasks, which cover non-favorite items.

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?

The wording implies when to use this tool: when the user wants aggregated favorites across all Asana workspaces. It does not explicitly state exclusions or alternatives, but the scope statement provides clear context for choosing this over project- or task-specific list tools.

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