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 of behavioral disclosure. It mentions SSH connectivity for remote hosts, which adds useful context about authentication and execution method. However, it doesn't cover critical behavioral traits such as whether this is a read-only operation, potential performance impacts, error handling, or output format details. For a tool with no annotations, this leaves significant gaps in understanding how it behaves.

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: it starts with the core purpose in the first sentence, followed by parameter details in a structured 'Args' section. There's no wasted text, and each sentence earns its place by providing essential information. It could be slightly more concise by integrating the parameter notes more seamlessly, but overall it's efficient.

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 is an output schema (which means the description doesn't need to explain return values) and no annotations, the description is moderately complete. It covers the purpose and parameter usage adequately. However, for a tool that interacts with system resources (potentially via SSH), it lacks details on permissions, error cases, or behavioral constraints, making it incomplete for safe and effective use by an AI agent.

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 adds meaningful semantics beyond the input schema, which has 0% description coverage. It explains that 'host' is optional and executes locally if not provided, and that 'username' is required if host is provided. This clarifies the conditional relationship between parameters and their practical usage, compensating well for the lack of schema descriptions. With 2 parameters and low schema coverage, the description does a good job of adding value.

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: 'Get CPU information and load averages.' This specifies the verb ('Get') and resource ('CPU information and load averages'), making it easy to understand what the tool does. However, it doesn't explicitly differentiate from siblings like 'get_hardware_info' or 'get_system_info', which might also provide CPU-related data, so it's not a perfect 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?

The description implies usage guidelines by explaining that the host parameter is optional and executes locally if not provided, and that username is required if host is provided. This gives some context for when to use remote vs. local execution. However, it doesn't explicitly state when to use this tool versus alternatives like 'get_hardware_info' or 'get_system_info', nor does it provide exclusions or broader context, so it's not fully explicit.

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