combell_ssh_set_enabled

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

Annotations already indicate mutation (readOnlyHint=false), idempotence, and non-destructiveness. The description adds the concrete effect of toggling SSH access, but it does not disclose edge behaviors such as whether existing SSH sessions are terminated or whether the change is applied asynchronously.

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, front-loaded sentence with no filler. It immediately communicates the action and target resource, making it easy for an agent to parse quickly.

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 simple two-parameter boolean setter, the description is mostly sufficient, especially with annotations covering safety and idempotence. However, it lacks guidance on sibling differentiation and does not mention any asynchronous behavior or response characteristics, which would improve completeness.

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 schema documents only domain_name, leaving enabled as a bare boolean. The description's 'enable or disable' provides the missing semantic for enabled, implying true enables and false disables. This compensates for the 50% schema coverage, though it does not explicitly name the parameter.

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 states a clear verb ('Enable or disable') and a specific resource ('SSH access on a Linux hosting'), so an agent can understand what the tool does. It does not explicitly differentiate from sibling SSH-key or linux_hostings_set_* tools, but the action is unambiguous enough.

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?

The description provides no guidance about when to use this tool versus related siblings such as combell_ssh_keys_add/delete or other linux_hostings_set_* tools. There are no alternatives, prerequisites, or exclusions mentioned, so usage context is only implied.

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