createAsanaTask

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the creation action but misrepresents custom_fields as optional when the schema marks it required, creating a contradiction with the schema. It does not mention return values, permissions, or side effects beyond creation.

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 that starts with the action verb and includes the key resource and optional details. Every word contributes to understanding, with no wasted text.

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?

With 6 parameters, a nested custom_fields object, and no output schema, the description is too minimal. It lacks information about what the tool returns, the fact that custom_fields is required, and any prerequisites like having projectId. The schema covers parameters but not the broader context needed for a create operation.

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 100% parameter descriptions, so the baseline is 3, but the description adds misleading information by labeling custom_fields as optional when it is actually required. The description does not add meaningful semantic value beyond the schema and introduces confusion.

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 verb 'Creates' and the resource 'a new task in the specified Asana project', distinguishing it from sibling tools like updateAsanaTask and readAsanaTask. The optional details listed (description, due date, assignee, custom fields) align with the intended use, even though custom_fields is actually required per schema.

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 use for creating tasks but does not explicitly state when to use it versus alternatives like updateAsanaTask or createAsanaComment. No exclusions or alternative tool names are provided, leaving the agent to infer context from the verb and sibling names.

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