listAsanaProjects

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

No annotations are present, so the description carries the full burden. It implies a read-only operation ('Retrieves') but does not disclose details like pagination, ordering, authentication needs, or error behavior. This is adequate for a simple list tool but leaves some behavioral aspects unstated.

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 a single 13-word sentence that is direct and front-loaded with the core action and resource. Every word earns its place, and it avoids redundancy.

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 tool with one required parameter and no output schema, the description covers the essential context: what it retrieves and the workspace scope. It could mention pagination or return format, but given the low complexity, it is sufficiently complete for an agent to select and invoke it correctly.

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 schema already documents workspaceId fully with 100% coverage, and the description merely references 'the specified Asana workspace' without adding new meaning. It meets the baseline but does not enrich the 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 tool's function: 'Retrieves a list of projects associated with the specified Asana workspace.' This uses a specific verb ('Retrieves') and resource ('list of projects'), and distinguishes it from sibling tools like listAsanaTasks and readAsanaProject by focusing on projects within a workspace.

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 description provides clear context: it is used to list projects in an Asana workspace. However, it does not explicitly mention alternatives or exclusions, such as using readAsanaProject for a single project or that it does not return tasks. The context is clear but lacks explicit when-not guidance.

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