reverse_shell_stop

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states the action without explaining side effects, whether it is idempotent, or what happens to the session after stopping. This is essentially a restatement of the tool name.

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 terse sentence, which is efficient, but it is under-specified to the point of being tautological. It does not add meaningful structure or detail beyond the tool name.

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 stop or termination tool, the description is minimally complete: it identifies the core action. However, it omits important context such as whether the operation requires an active session, potential side effects, or how to identify the correct session. With no annotations or output schema, this is insufficient for reliable use.

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 description coverage is 0%, and the description does not mention the required 'session_id' parameter. It fails to clarify what session_id represents or how to obtain it, leaving the agent to guess from the parameter name alone.

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 'Stop reverse shell.' explicitly states the action (stop) and the resource (reverse shell), making the purpose unambiguous. It also distinguishes from sibling tools like reverse_shell_listener_start or reverse_shell_status by its clear imperative to terminate.

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 regarding when to use this tool versus alternatives, such as when a session is no longer needed or to clean up after pivoting. The description simply says 'Stop reverse shell' with no context about session state or prerequisites.

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