task_create

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

Annotations indicate destructiveHint=false, so the tool is safe. The description adds that tasks are created for 'yourself or another agent' and 'survive across sessions', providing context about persistence and multi-agent use. No contradiction with 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?

The description is concise: one lead sentence explaining purpose, one sentence on usage guidance, and a bulleted Args list. Every sentence adds value. No fluff.

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?

Given 7 parameters (1 required), 100% schema coverage, and an output schema, the description covers all necessary aspects: purpose, when to use, each parameter's meaning, and a pre-use check. It is complete for an agent to effectively invoke this tool.

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% (all 7 parameters have descriptions), so baseline is 3. The description adds extra meaning: for title, it says 'Short imperative description'; for expected_outcome, 'What done looks like — specific, observable result'; and for depends_on, 'Task IDs that must be completed before this task is unblocked.' These elaborations go beyond the schema, justifying a 4.

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 explicitly states 'Create a task for yourself or another agent to pick up.' It clearly identifies the action (create) and the resource (task). This distinguishes it from sibling tools like task_list (list tasks) or task_update (update tasks).

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 provides clear guidance: 'Use when there's a discrete unit of work that should be tracked, may be done by a different agent, or needs to survive across sessions. Check task_list() for duplicates before creating.' This tells the agent when to use the tool and gives a precondition (check for duplicates), effectively distinguishing it from alternatives.

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