reverse_shell_status

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

No annotations are present, so the description must disclose behavioral traits. The word 'status' weakly implies a read-only query, but it does not describe what the tool returns, whether it requires an active session, or how it behaves with an invalid/empty session_id. This lack of detail leaves the agent guessing.

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 only three words long, which is under-specification rather than appropriate conciseness. It lacks essential details, so every word is effectively wasted by not conveying meaningful information. It is short but not effectively structured for usability.

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?

With no annotations and no output schema, the description is the only source of context. It provides no explanation of what 'reverse shell status' means, no return format, no error conditions, and no relationship to sibling reverse_shell_* tools. The description is completely inadequate for correct invocation.

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 'session_id' at all. The parameter is left entirely unexplained; its type and default are in the schema, but its meaning and how it affects behavior are absent from the description. The description fails to compensate for the low schema coverage.

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 'Reverse shell status' is essentially a restatement of the tool name, providing no verb or specific resource/action. It does not explain what 'status' refers to (e.g., whether it checks a session, a listener, or all active shells), making it a tautology rather than a clear purpose.

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 use this tool vs alternatives like 'ssh_session_status' or 'ctf_status'. The description offers no context for choosing this tool, no prerequisites, and no exclusions. It merely names the tool's function without explaining usage scenarios.

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