ssh_get_disk_usage

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. It implies a read-only remote operation but does not disclose authentication requirements, whether credentials must be pre-configured, timeouts, or side effects, leaving the agent with only the tool name to infer 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?

The description is a single front-loaded sentence with no filler. It is appropriately sized for the basic action, though it is too sparse elsewhere rather than too verbose.

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?

An output schema exists, so return values need not be described, but the definition still lacks required context: credential prerequisites, host format, and differentiation from the non-SSH disk usage sibling. For a remote-execution tool with no annotations, this is insufficient.

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 0% description coverage, and the description does not explain the 'hostname' parameter at all. It does not clarify whether hostname is an IP, DNS name, inventory alias, or how credentials are associated with it.

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 specific verb and resource ('Get disk usage information') and adds the target ('Linux host'), so the agent can tell what the tool does. However, it does not distinguish this SSH-based tool from the sibling 'get_disk_usage', which appears to cover similar functionality.

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 tools, especially 'get_disk_usage' or 'ssh_get_system_info'. It also omits prerequisites such as whether SSH credentials must be configured first via 'ssh_setup_credentials'.

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