get_ssh_host

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

With no annotations, the description must carry the full burden of behavioral disclosure. It clearly states a read-only intent ('Get'), but provides no details about return format, error behavior, or whether it includes status information. The description is minimal but not misleading, so a middle score is appropriate.

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 a single, well-structured sentence that immediately states the action and target. There is no redundant text, and the key information is front-loaded.

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?

For a simple one-parameter read operation with a straightforward semantic, the description is largely sufficient. No output schema exists, but the description's clarity about retrieving a host by ID gives enough context. It could be enhanced by explicitly stating return value or differentiating from get_host_status, but such additions are not critical for this low-complexity 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?

The schema already covers the single parameter 'id' with type integer and description 'The SSH host ID', providing 100% coverage. The description's phrase 'numeric ID' adds no new meaning beyond what the schema states, so it meets the baseline without adding extra value.

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 ('Get') with a clear resource ('a single SSH host') and a unique qualifier ('by its numeric ID'). This clearly distinguishes it from sibling tools like list_ssh_hosts (which retrieves multiple) and get_host_status (which focuses on status).

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 implies that the tool should be used when you have a numeric ID and need a single host, but it does not explicitly state when to use it vs. alternatives. There is no mention of exclusions or references to sibling tools, leaving the usage context only implicit.

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