linux_ssh_config_generator

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

Annotations (readOnlyHint=true, destructiveHint=false) are reinforced and expanded: the description clarifies it only builds config text, never writes files, edits, or connects. It also mentions security warnings for weak settings, which adds beyond annotations.

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 somewhat lengthy but well-structured: it starts with purpose, then behavioral constraints, then parameter explanations, and ends with usage guidance. Every sentence adds value, though a slight reduction in verbosity would improve conciseness.

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?

Given the complex nested schema and presence of an output schema, the description fully covers the tool's purpose, behavior, parameter details, and presets feature. It also mentions security warnings and sibling tools, making it complete for an AI agent.

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?

Despite 100% schema coverage, the description adds significant meaning: explains 'operation' modes (generate vs presets), describes what presets returns, and summarizes the key client and server settings. It adds context about security warnings not in the schema.

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 clearly states it generates OpenSSH client and/or server config text from structured definitions. It distinguishes itself by explicitly stating it never writes files, connects to hosts, or touches the SSH agent, which differentiates it from the sibling linux_web_server_config_generator.

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 clear when-to-use guidance: 'Use this for OpenSSH connection and daemon config' and implies an alternative ('use linux_web_server_config_generator'). It also explicitly states what it does not do, helping agents avoid misuse.

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