ssh_set_option

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

With no annotations provided, the description must carry the full burden of behavioral disclosure. It indicates a mutation ('set') but does not disclose whether the change persists, affects only the current session, requires specific privileges, or what happens to existing options. No side effects or usage details are mentioned.

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 concise sentence that is front-loaded and contains no fluff. It is efficient, though it provides minimal additional value beyond the tool name itself.

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 mutation tool with no annotations and no output schema, the description is too sparse. It does not explain the return value, the scope of change (persistent vs. session-only), or relate to sibling tools like ssh_get_config. However, the parameter schema is fully described and the operation is simple, preventing a score of 1.

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 already describes both parameters (key, value) with 100% coverage. The description adds no extra semantic information about valid keys, value formats, or examples, so it does not go beyond the baseline for well-covered schemas.

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 'Set an SSH configuration option' with a specific verb (set) and resource (SSH configuration option). It is clear and unambiguous, but it does not explicitly differentiate from sibling tools beyond the verb, and it largely restates the tool name.

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?

No guidance is given on when to use this tool versus alternatives like ssh_get_config, or any context about session requirements or scope. There is no mention of exclusions or alternative approaches.

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