Stop the current task

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

With no annotations, the description must carry the behavioral burden. It discloses the primary effect and the important constraint that no new task is started. It does not mention what happens if no task is running, whether the stop is reversible, or what the response looks like, but the core behavior is clear.

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?

A single, front-loaded sentence with no filler. It states the action and its scope immediately, and the additional clause adds meaningful distinction without bloat.

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 simple zero-parameter, no-output-schema action, the description is nearly sufficient. It explains the action and its non-cascading nature. A small gap is the lack of guidance on edge cases like stopping when no task is current, but the tool's simplicity keeps this minor.

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 tool has zero parameters, so the baseline is 4. The description correctly avoids inventing parameters and provides enough context about what operation is performed.

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 ('Stops') with a clear resource ('the currently running task') and explicitly notes it does not start another task. This distinguishes it from sibling tools like sp_task_start and sp_task_control_set_current.

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 makes the use case clear: invoke when you want to halt the currently running task and remain idle. However, it gives no explicit guidance about when not to use this tool or how it differs from related alternatives such as sp_task_delete or sp_task_update.

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