Linux MCP Server

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It describes the execution context (local vs. remote via SSH) and parameter dependencies, but doesn't mention important behavioral aspects like whether this requires elevated privileges, what format the output takes, potential performance impact, or error conditions.

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 and front-loaded with the core purpose first, followed by parameter explanations. Every sentence earns its place, though the formatting with 'Args:' header and bullet-like structure could be slightly more polished.

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's moderate complexity (process listing with remote/local options), no annotations, and the presence of an output schema, the description provides good coverage of the tool's purpose and parameter usage. However, it could benefit from mentioning typical use cases or output characteristics to be fully complete.

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?

With 0% schema description coverage, the description fully compensates by explaining both parameters in detail: 'host' as 'Remote host to connect to via SSH (optional, executes locally if not provided)' and 'username' as 'SSH username for remote host (required if host is provided)'. This adds crucial semantic meaning beyond the bare schema.

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 specific verb ('List') and resource ('running processes'), including what information is provided ('CPU and memory usage'). It distinguishes itself from sibling tools like 'get_process_info' by focusing on listing rather than getting detailed info about a specific process.

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 clear context about when to use certain parameters (host and username for remote execution vs. local execution if not provided). However, it doesn't explicitly state when to use this tool versus alternatives like 'get_process_info' or other monitoring tools in the sibling list.

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