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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds that data comes from a fixed GET /servers/{id}/hardwareinfo endpoint, but says nothing about auth requirements, rate limits, or whether values are cached/live. Adequate but not rich.

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?

One content sentence plus an endpoint reference, with the highest-value information (returned fields) front-loaded and zero filler.

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?

There is no output schema, so the description correctly compensates by enumerating the returned fields, and annotations carry the read-only safety profile. It is nearly complete for a single-param read tool; only the absence of usage routing against sibling health/stats tools is a real gap.

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 coverage is 100% and the single server_id parameter is fully documented in the schema, including a pointer to runcloud_list_servers. The description adds no further parameter meaning, so the baseline 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?

States a specific verb+resource (get server hardware info) and enumerates exactly what is returned: kernel version, CPU model/cores, memory and disk totals/free, load average, uptime. This field list implicitly distinguishes it from sibling tools like runcloud_get_server_health and runcloud_get_server_stats, but no sibling is named explicitly, so it stops short of a 5.

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?

Provides no when-to-use guidance and does not contrast itself with the closely related runcloud_get_server, runcloud_get_server_health, or runcloud_get_server_stats. The agent must infer the distinction from the returned-field list alone.

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