sc:task

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

No annotations are provided, so the description must convey behavioral traits. It mentions 'cross-session persistence' but does not explain side effects, required permissions, or potential impacts. It includes 'Category: operations' and 'Priority: IMPORTANT', but these are more metadata than behavioral disclosure. No information about authentication, rate limits, or destructive actions.

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 a single sentence, which is concise, but it includes extraneous information like 'Category: operations, Priority: IMPORTANT' that seems like metadata rather than explanatory text. It could be restructured to be more informative without adding length.

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 tool has three parameters and no output schema. The description does not explain what the tool returns, nor does it provide context on how to use the flags or interpret results. The lack of output schema makes it incomplete; the agent has no information about the response format.

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?

All three parameters have descriptions in the input schema (100% coverage). The description adds no additional meaning beyond the schema; it merely reiterates the flags and preferred agents. The baseline is 3 since schema coverage is high and the description adds minimal extra value.

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 states 'Enhanced task management with cross-session persistence', clearly indicating task management with persistence. The input schema hints at multiple operations (create, status, etc.), but these are not explicitly listed in the description. The tool name 'task' distinguishes it from siblings like analyze or build, but the description does not differentiate from sc:workflow or others.

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 guidance on when to use this tool versus alternatives. The description does not mention use cases, prerequisites, or exclusions. The sibling tools list includes 21 other tools, but no comparative advice is provided.

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