add_task

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

With no annotations, the description carries the behavioral disclosure burden. It does add a meaningful behavior: 'Fails if the id exists,' which warns against duplicate creation. However, it does not mention other side effects, permissions, downstream consequences, or the non-idempotent nature beyond that one failure mode.

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 short sentences with no filler. The core action is front-loaded, and each subsequent sentence provides distinct useful information about input format and duplicate-id failure.

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 schema already documents all 17 parameters and an output schema exists, so return details are not required. Still, this is a complex mutation tool with many siblings and no annotations; the description omits any selection guidance, prerequisite context, or broader side-effect information, making it minimally adequate rather than complete.

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 adds value by explicitly stating that deps/scope accept an array or a comma string, which clarifies the anyOf schema type, and by noting the id uniqueness failure condition.

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 'Create a task,' a clear verb+resource statement that distinguishes this tool from edit, amend, close, delete, and start siblings. It does not explicitly compare itself to add_target or other creation-adjacent tools, so it falls short of full differentiation.

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?

Usage is implied through 'Create a task' and the tool name, but there is no explicit guidance about when to choose add_task over edit_task, amend_task, or add_target. No exclusions or alternative-selection conditions are provided.

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