searchAsanaTasks

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

There are no annotations, so the description bears full responsibility for disclosing behavior. It misleadingly states that filtering by completion status is optional, but no such parameter exists, and workspace is required rather than optional. It also doesn't mention return values or side effects. This erroneous information undermines transparency.

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 one concise sentence with no redundant phrasing. It could be slightly improved by removing the inaccurate filter list, but the length and structure are appropriate.

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 search tool with no output schema, the description should cover what results look like, any pagination or limits, and any behavioral nuances. It does none of that, and the filter inaccuracy adds confusion. Given the tool's complexity (3 params, no output schema), the description is incomplete.

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 already documents all three parameters thoroughly (100% coverage), so the description adds little value. Worse, it introduces a non-existent 'completion status' filter and refers to workspace as optional when it is required, which could confuse an AI agent. Therefore it doesn't meaningfully enhance 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 searches for tasks in Asana, which is a specific verb+resource. It also lists optional filters, but the mention of 'completion status' is inaccurate since no such parameter exists in the schema, and 'workspace' is actually required. This minor inaccuracy prevents a 5, but the core purpose is unambiguous.

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 implies the tool is used when you need to find tasks by a search term, with optional filters. However, it provides no explicit guidance on when to choose this over listAsanaTasks or other task-related tools, nor any prerequisites or limitations.

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