searchAsanaTasks

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

No annotations exist, so the description carries the full burden. It contradicts the schema by labeling workspace as optional and mentions a completion status filter that does not exist in the schema, misleading the agent.

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, reasonably concise sentence with the primary action front-loaded. It does not waste many words, though the inaccurate qualifier slightly detracts.

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?

The description omits key details such as return format, pagination, search behavior, and any constraints. The misleading filter information leaves the tool under-specified for an agent with no annotations or output schema.

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 covers all parameters with descriptions, providing a baseline of 3. However, the description adds inaccurate 'completion status' context not represented in the schema, reducing semantic clarity.

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 it searches for tasks matching a search term, distinguishing it from list/read Asana tools. However, it mischaracterizes workspace as an optional filter when it is actually required, undermining precision.

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 searchAsanaTasks versus listAsanaTasks or readAsanaTask. The description does not state exclusion criteria or alternatives.

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