list_asana_projects

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

With no annotations, the description carries full burden for behavioral disclosure but only states 'List projects in an Asana workspace.' It fails to mention key behaviors like pagination, the ability to include archived projects, authentication needs (api_key), error handling, or performance characteristics.

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 concise sentence with no redundancy. However, it could be improved by including structured details about parameters or behavior without sacrificing brevity. Currently, it is too minimal.

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?

Given the tool has 4 parameters and no output schema, the description is insufficient. It does not explain the return format, pagination (despite a 'limit' parameter), or the role of 'api_key'. The description lacks essential context for an agent to use the tool effectively.

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 provides descriptions for 3 of 4 parameters (75% coverage), but the description adds no additional meaning. The 'api_key' parameter lacks a description in both schema and tool description. The tool description should clarify parameter usage, especially for authentication and optional filters.

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 lists projects within an Asana workspace. The verb 'List' and resource 'projects' are specific, and the scope is well-defined. It effectively distinguishes this tool from siblings like 'list_asana_tasks' or 'search_asana_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?

No guidance is provided on when to use this tool versus alternatives. There is no mention of when to prefer listing projects over searching or creating them, nor any exclusions. The description lacks context on prerequisites or use cases.

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