sp_set_current_task

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

No annotations are present, so the description must carry behavioral disclosure. It reveals the state-changing nature and the null-to-clear behavior, but does not mention side effects such as whether setting a new current task stops the previous one, whether time tracking is affected, or what the operation returns.

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?

One short sentence, front-loaded with the primary action and a compact parenthetical for the null case; no filler or redundancy.

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?

For a one-parameter setter this is nearly sufficient, but the lack of any note about its relationship to sp_start_task/sp_stop_current_task and the effect on time-tracking state leaves a moderate gap, especially with no annotations or 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 coverage is 100%, so the schema already documents taskId and the null special value. The description's '(or clear)' reinforces that behavior but adds no new syntax or format information.

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 uses a specific verb ('Set') and a precise resource ('currently active task'), including an explicit '(or clear)' branch for the null case. It is unambiguous on its own, though it does not explicitly differentiate itself from siblings like sp_start_task or sp_get_current_task.

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?

There is no statement about when to choose sp_set_current_task over siblings such as sp_start_task or sp_stop_current_task. The description only defines what the tool does, leaving the selection context to inference.

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