Create a temporary SSH connection without saving to database

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

Annotations already indicate this is not read-only, not idempotent, and not destructive. The description adds the key behavioral fact that nothing is saved to the database and that a temporary host configuration is returned, but it does not explain connection lifetime, cleanup, or side effects beyond that.

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 short and places the most important distinguishing feature ('without saving to database') first. However, the first sentence closely repeats the tool name and title, so it does not fully earn its place.

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 10 parameters and no output schema, the description should clarify what the returned 'temporary host configuration' contains and how it should be used. It also leaves the meaning of 'temporary' ambiguous—how long the connection or config remains valid is unspecified, which is a significant gap for an ephemeral tool.

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?

Schema description coverage is 100%, so the schema already documents all ten parameters, including conditional requirements such as 'required if authType is key'. The tool description adds no additional parameter-level meaning, so the baseline score of 3 applies.

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 a specific verb ('Create') and resource ('temporary SSH connection') with an explicit scope qualifier ('without saving to database'). This clearly distinguishes it from persistent host creation tools like termix_hosts_create_ssh_host.

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 phrase 'without saving to database' implies the use case of needing a non-persistent, ephemeral connection, but the description does not explicitly name alternatives or state when not to use this tool. The usage context is implied rather than actionable.

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