Linux MCP Server

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

With no annotations provided, the description carries full burden for behavioral disclosure. It mentions SSH connectivity behavior (local vs remote execution) which is valuable, but doesn't describe what 'list' actually returns - format, structure, or content of the output. For a tool with an output schema (which exists but isn't described here), the description should at least hint at what information is returned about block devices and partitions.

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 perfectly structured and concise. The first sentence states the core purpose, followed by clear parameter documentation in a well-formatted 'Args:' section. Every sentence earns its place, with no redundant information. The information is front-loaded with the main purpose stated first.

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 the tool has an output schema (which handles return values), the description provides good contextual completeness. It covers the core purpose and fully documents both parameters. The main gap is lack of behavioral context about what 'listing' actually entails - what information is returned about devices. However, since output schema exists, this is less critical than for tools without output schemas.

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 description provides excellent parameter semantics beyond the schema. With 0% schema description coverage and 2 parameters, the description fully documents both parameters: explaining that 'host' is optional for remote SSH connection (defaulting to local execution), and that 'username' is required conditionally based on whether host is provided. This completely compensates for the lack of schema descriptions.

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 action ('List') and resource ('block devices and partitions'), making the purpose immediately understandable. It distinguishes itself from siblings like 'get_disk_usage' or 'get_hardware_info' by focusing specifically on block-level storage devices rather than usage metrics or general hardware. However, it doesn't explicitly contrast with all siblings, keeping it from a perfect score.

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 provides implied usage guidance through the parameter explanations - indicating this tool can execute locally or remotely via SSH. However, it doesn't explicitly state when to use this versus alternatives like 'get_disk_usage' for capacity information or 'get_hardware_info' for broader hardware details. No explicit 'when-not' scenarios or sibling tool comparisons are provided.

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