linux_ssh_disable

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

With no annotations, the description must carry the transparency burden. It does disclose that this is a write operation requiring confirmation, which is valuable. However, it does not say what confirmation entails, which parameters are involved, or what happens to existing SSH connections/settings when disabled.

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 sentence with no filler; 'Disable SSH service' is front-loaded. It is efficiently written, though the brevity leaves room for more structured confirmation detail.

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 write tool with three undocumented parameters and no annotations, the description is too sparse. It fails to explain the confirmation workflow, required parameters, side effects, or how to re-enable the service; the sibling linux_ssh_enable exists but is not referenced.

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%, so the description needed to explain user_code, confirm_token, and confirmation_id; it does not. The phrase 'requires confirmation' only hints at the purpose of the confirmation fields, leaving parameter semantics largely to inference from their names.

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 gives a specific action ('Disable') and resource ('SSH service to the Linux environment'), making the tool's intent unmistakable. It is implicitly distinguished from the sibling linux_ssh_enable by being the inverse operation, though it doesn't explicitly name the alternative or its scope.

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 versus linux_ssh_enable, linux_ssh_port, or mngt_sshport. The phrase 'requires confirmation' hints at the invocation flow but not at conditions, prerequisites, or exclusions. This is effectively no usage-direction.

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