launchQuickTask

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

The description adds the 5s cooldown per preset beyond the annotations. Annotations already indicate non-destructive and open-world behavior. No contradiction exists.

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 extremely concise with three short sentences, front-loading the purpose and adding key behavioral info without waste.

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 the complexity of launching a task, the description lacks details on return values, error handling, or task lifecycle. The schema covers parameters well, but the tool's overall behavior is only partially described.

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?

The input schema has 100% coverage with enums and descriptions. The description adds no further parameter meaning, so baseline 3 is appropriate.

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 it launches a Claude task from a named preset and mentions it uses the same dispatch path as sidebar and CLI, which distinguishes it from other task tools like runClaudeTask or resumeClaudeTask, though not explicitly.

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?

No explicit when-to-use or when-not-to-use guidance is provided. The cooldown constraint is mentioned, but there is no comparison with sibling tools like runClaudeTask to guide selection.

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