cancel_command

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

No annotations are supplied, so the description carries the entire burden of behavioral disclosure. It does not say whether cancellation is immediate or cooperative, whether it is idempotent on an already-finished command, whether partial output remains retrievable via get_command_output, or what the response contains. For a state-mutating tool this is a substantial gap, though the word 'Cancel' does at least convey the mutation intent.

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, front-loaded sentence with no redundant clauses or filler. It is efficient, though the efficiency comes at the cost of the detail the description should have carried.

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 mutation tool with no annotations, no output schema and an undocumented required parameter, the definition leaves out everything an agent needs to call it safely and interpret the result. The one identifier it consumes is unexplained, and the effect on subsequent calls to get_command_output or get_command_status is unstated.

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 single parameter 'id' has zero schema description coverage, and the description adds no meaning beyond the bare schema. It never states that the id is the command identifier returned by execute_command or execute_command_async, which is the one clarification an agent actually needs.

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?

States a specific verb and resource: 'Cancel a running command.' An agent can immediately tell this is the command-termination tool, distinct from execute_command or get_command_status by verb alone. It stops short of 5 because it never names the neighbours it is meant to be chosen over.

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 guidance on when to cancel rather than wait (wait_for_command) or poll (get_command_status), and no mention of preconditions such as the command still being in a running state. The agent must infer the selection rule from the tool name alone.

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