ssh_host_list

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

No annotations are provided and the description only states 'list', implying a read operation but does not disclose safety, side effects, or requirements. With zero annotations, the description should explicitly note read-only behavior.

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?

Description is concise, front-loading the purpose in one sentence followed by a clear list of return fields. Efficient but could be slightly more compact.

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?

Covers return structure but lacks usage context and behavioral details. For a simple list tool with output schema, it is minimally adequate but leaves gaps in guidance and transparency.

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 has 0 parameters, so baseline is 4. The description adds value by detailing the return structure (hosts with key, alias, description) beyond 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 explicitly states 'List all configured SSH hosts' using a specific verb and resource, distinguishing it from sibling tools like ssh_conn_host_info which presumably provides detailed host information.

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 on when to use this tool versus alternatives like ssh_conn_host_info or ssh_host_remove; lacks context for selection.

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