Linux MCP Server

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

No annotations are provided, so the description carries the full burden. It mentions remote execution via SSH and local fallback, which is useful behavioral context. However, it doesn't disclose critical details like authentication methods (e.g., password, key-based), error handling, performance characteristics, or what the output contains beyond the listed hardware components. For a tool with no annotations, this leaves significant gaps in understanding its 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 appropriately sized with two clear sections: a purpose statement and parameter explanations. Every sentence adds value, with no redundant information. It could be slightly more front-loaded by integrating parameter details into the main flow, but overall it's efficient and well-structured.

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?

Given that there's an output schema (which should document return values), the description doesn't need to explain outputs. However, with no annotations and 0% schema description coverage, the description provides basic purpose and parameter guidance but lacks depth on behavioral aspects like error conditions, security implications of SSH usage, or performance considerations. It's minimally adequate but has clear gaps for a tool that interacts with system hardware.

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 description coverage is 0%, so the description must compensate. It adds meaningful semantics for both parameters: explaining that 'host' is optional for remote SSH connection (defaulting to local execution) and that 'username' is required if host is provided. This clarifies usage beyond the bare schema, though it doesn't cover all potential edge cases like port numbers or authentication details.

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 clearly states the tool's purpose with a specific verb ('Get') and resource ('hardware information'), listing specific components like CPU architecture, PCI devices, USB devices, and memory hardware. However, it doesn't explicitly differentiate from sibling tools like get_cpu_info or get_memory_info, which appear to be more specialized versions of this broader tool.

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 usage through the parameter documentation in the Args section, explaining when to provide host and username for remote execution versus local execution. However, it lacks explicit guidance on when to use this tool versus alternatives like get_cpu_info or get_memory_info, and doesn't mention any prerequisites or exclusions beyond the SSH parameters.

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