Create SSH host

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

The description only restates that it creates a new SSH host configuration, which is already evident from the name and annotations like readOnlyHint=false. It does not disclose consequences, default values, persistence behavior, or what happens if required fields are missing. With annotations present, the description adds little behavioral value beyond the structured metadata.

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 text is short and front-loaded, but this is under-specification rather than concise writing. A 42-parameter creation tool needs at minimum a summary of what the tool accomplishes and what the key fields mean. The one-sentence description is too sparse to be considered appropriately sized for the schema complexity.

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?

There is no output schema and no return value documentation, making the description the only place to explain effect and results, and it fails to do so. It also omits the relationship to update, temporary connections, bulk import, naming defaults, and folder hierarchy options. This is critically incomplete for a creation endpoint with this many optional fields.

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 has 42 parameters but only 24% documented, so the description needed to compensate for the enormous undocumented surface. The description mentions no parameters at all and gives no hints about ip/port requirements, authType options, password vs key vs credential, or essential optional fields. An agent inspecting this tool would be left almost entirely dependent on a mostly undocumented 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 uses the verb 'create' with a clear resource, 'SSH host configuration,' which makes the core operation obvious. It is distinguishable from siblings like update_ssh_host and create_temporary_ssh_connection_without_saving because it emphasizes creating a new persisted configuration. It is slightly tautological with the title, but it adds the key 'new configuration' nuance.

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 update_ssh_host, create_temporary_ssh_connection_without_saving, or bulk_import_ssh_hosts. The agent has to infer usage from the tool name alone. No alternatives are named or excluded.

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