Enable Ssh

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

No annotations are provided, so the description carries the full disclosure burden and mostly fails it: nothing is said about permission requirements, whether the change persists across reboots, or the security impact of exposing SSH. It does earn minor credit for clarifying that the tool both enables and disables (despite the name `enable_ssh` implying one direction only), which matches the `enabled` flag.

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?

A single short sentence with no padding and the action front-loaded. It is efficient but so terse that it reads as a label rather than a definition; slightly more substance could fit without bloat.

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?

An output schema exists, so return values need not be explained, but for a security-relevant service toggle with zero annotations the description should say more about effects and prerequisites. The agent knows what the tool toggles but not when or under what constraints to call it.

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 100%, with both `enabled` and `port` documented inline (including the port default of 22), so the schema does the heavy lifting. The description adds no meaning beyond the schema, which is the baseline-3 case.

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 names a specific resource (SSH service) and the exact action pair (enable/disable), which the agent can map directly onto the `enabled` boolean. It is clear in isolation, but it does nothing to distinguish this tool from closely-related siblings such as enable_telnet and enable_ftp.

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 when-to-use guidance, no prerequisites (e.g. required admin privileges, whether SSH must be off/on before related operations), and no mention of alternatives or when-not-to-use. The agent gets no routing signal other than the obvious name match.

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