htb_stop_machine

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

The description indicates a destructive action ('terminate') but fails to disclose side effects such as loss of state, required permissions, or reversibility. With no annotations, the description bears the full burden and does not adequately inform the agent of behavioral traits.

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 at one sentence, front-loaded with the verb. While no words are wasted, some additional context could be added without sacrificing conciseness.

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 single parameter and no output schema, the description is minimally complete but lacks essential context such as error handling, success indicators, or the requirement that the machine must be currently spawned. It does not reference sibling tools like htb_active_machine for context.

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 only parameter `machine_id` is an integer with no schema description (0% coverage). The phrase 'by id' adds minimal value beyond the parameter name. No guidance on where to obtain the ID or constraints is provided.

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 the action 'Terminate' and the resource 'a spawned machine or Starting Point VM by id'. It distinguishes from sibling tools like htb_spawn_machine and htb_reset_machine by specifying termination, making the purpose unambiguous.

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 guidance is provided on when to use this tool versus alternatives such as htb_reset_machine. There is no mention of prerequisites, conditions for use, or scenarios where termination is appropriate.

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