linux_ssh_config_generator

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

Without annotations, the description fails to disclose behavioral traits like overwriting behavior, required permissions, or side effects. It only lists features but does not explain what happens during generation.

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?

Relatively concise with two main sentences. Some redundancy in 'Menu ID' and 'SSH Config Generator', but overall front-loads purpose efficiently.

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 complexity (nested objects, 3 required params, no output schema), the description is incomplete. It defers to describe_tool and lacks parameter details, making it insufficient for safe invocation.

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?

Parameter descriptions are absent from both schema and description. The description does not explain 'operation', 'mode', or 'serverSettings' fields, leaving the agent without enough context to set them appropriately.

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?

Description clearly states it generates SSH client and server config files with specific security features like ProxyJump, port forwarding, key auth, hardened ciphers, and fail2ban settings. It distinguishes itself from sibling tools like bash_script_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?

No explicit guidance on when to use vs alternatives. The description mentions using describe_tool for full guidance, but does not provide direct usage context or exclusions.

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