tasks_tasks_insert

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

Annotations already establish that this is a mutating, non-idempotent, non-destructive operation. The description adds useful placement behavior beyond the schema, but it does not disclose return values, authorization needs, or side effects; the annotation coverage keeps this at a solid midpoint.

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 short sentences with no filler. The core action is front-loaded, and the placement guidance is compact and directly actionable.

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 all seven parameters fully documented in the schema and annotations covering mutation and idempotency, the description is sufficient for correct invocation. The only minor gap is the lack of mention of the response/return value, which is not covered by an 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 description coverage is 100%, so the baseline is 3. The description's parent/previous wording largely restates the schema descriptions rather than adding new semantic meaning, so it does not raise the score.

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 opens with a specific verb and resource: 'Create a new task.' The second sentence adds unique creation-specific behavior (nesting via parent, ordering via previous), clearly distinguishing this insert tool from the update, move, list, and delete siblings.

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 gives direct usage guidance for the placement parameters: 'Use parent to nest as a subtask, previous to position after a sibling.' It does not explicitly name alternative tools, but 'Create a new task' makes the tool's role and when to choose it clear.

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