Enable autostart for SSH configuration

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

The annotations already indicate this is a state-changing operation (readOnlyHint=false) and not idempotent, but the description adds no behavioral context beyond that: it does not explain whether the autostart setting persists, applies immediately, requires a valid configuration, or can be reverted. No contradiction with annotations, but no useful disclosure is added either.

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 very short and front-loaded, but it is redundant: the first and second sentences essentially repeat the same statement, with only 'specific' added in the second. It earns points for brevity but not for efficient use of every sentence.

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 one parameter, no output schema, and a narrow operation, the definition could be adequate if it clarified that sshConfigId is required and what 'autostart' affects. It does neither, leaving an agent without enough context to know whether a call without the parameter is valid or what persistent effect will occur.

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 input schema contains one property, sshConfigId, with no description, and the schema marks zero parameters as required. The description never mentions sshConfigId or states that it must be supplied to identify the target configuration. The property name is somewhat self-explanatory, but the description does not compensate for the 0% schema description 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 states a clear action ('enable autostart') on a specific resource ('SSH configuration'), and the second sentence narrows this to 'a specific SSH configuration.' This is sufficient to distinguish the operation from the sibling get_autostart_status tool, though it does not explicitly name that sibling or provide further scope detail.

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 alternatives such as termix_hosts_get_autostart_status, nor any mention of prerequisites like an existing SSH configuration or whether the enabling is only for saved/non-temporary hosts. The intended use is only implied by the action verb and tool name.

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