Add Task To Section

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

Discloses default top placement, the effect of insert_before/insert_after, and that it returns a success message. Annotations already indicate non-read-only, non-destructive, idempotent behavior; description adds placement specifics without contradicting annotations.

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?

Three sentences, each with a distinct purpose: action, behavior, and alternative. No 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?

Sufficient for a simple move operation with complete schema and annotations. The description covers key behavioral aspects and provides an alternative for creation-time placement.

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 descriptions cover all parameters (100%). The description adds default placement behavior (top of section) that is not in the schema, enhancing understanding of insert_before/insert_after.

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 moves a task into a specific section within a project, using a specific verb and resource. It distinguishes from sibling tools like asana_add_project_to_task by focusing on section placement.

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?

Provides explicit guidance to prefer asana_create_task with memberships when placing tasks at creation time. However, it does not fully cover when to use this tool versus other update/move alternatives.

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