ssh_get_system_info

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

No annotations are provided, so the description must carry the full behavioral burden, yet it only implies a read operation. It does not mention SSH authentication requirements, credential setup dependencies, failure behavior, or scope/limitations, despite sibling tools for credential management.

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 front-loaded sentence with no wasted language. However, its brevity comes at the cost of useful detail rather than achieving efficient completeness.

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 an SSH-based tool with no annotations, undocumented parameter semantics, and siblings that manage credentials, the description is insufficient. The existence of an output schema reduces the need to explain return values, but authentication prerequisites and hostname format are missing.

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 single hostname parameter has 0% schema description coverage, and the description does not explain its expected format or meaning beyond implying a Linux host target. It does not clarify whether hostname means an IP address, DNS name, or SSH config alias.

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 states a clear verb and resource: get basic system information from a Linux host. It is understandable, but it does not differentiate itself from sibling tools such as ssh_get_running_processes, ssh_get_disk_usage, or ssh_get_services, and 'basic system information' remains somewhat vague.

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 the many sibling SSH tools that retrieve specific system details. The only implied constraint is that the target is a Linux host, with no alternatives, prerequisites, or exclusions mentioned.

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