tasks_tasks_insert

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

Annotations indicate readOnlyHint=false, so the write intent is clear. The description adds behavioral details on nesting and ordering beyond annotations, but does not mention return behavior or potential side effects (e.g., response shape, idempotency).

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?

Two concise sentences, front-loaded with the primary action, zero waste. Every word serves a purpose.

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 is complete for the tool's purpose given its complexity. It covers the core creation action and optional nesting/ordering. It could be improved by mentioning the return value (e.g., created task ID), but this is not critical.

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 coverage is 100% with good individual parameter descriptions. The description adds value by explaining how 'parent' and 'previous' interact (nesting vs. ordering), which goes beyond the schema's isolated descriptions.

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 creates a new task and explains how the 'parent' and 'previous' parameters enable subtask nesting and sibling positioning, distinguishing it from siblings like tasks_tasks_move and tasks_tasks_update.

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 explains the core action and when to use the 'parent' and 'previous' parameters, but it does not explicitly state when not to use this tool or provide alternatives for similar tasks (e.g., updating instead of inserting).

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