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 discloses that the tool can execute locally or remotely via SSH, which is useful behavioral context. However, it lacks details on permissions needed, rate limits, error handling, or what the output contains beyond the listed fields, leaving gaps in behavioral understanding.

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 in the first sentence. The Args section is necessary due to low schema coverage, but the structure is clear and efficient, with no redundant or wasted sentences.

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 (2 parameters, no annotations, but with an output schema), the description is reasonably complete. It covers the purpose, parameters, and usage context. Since an output schema exists, it need not explain return values, but it could benefit from more behavioral details like error cases or output format hints.

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: 'host' is explained as optional for remote SSH connection (defaults to local), and 'username' is required if host is provided. This clarifies usage beyond the schema's basic types and defaults, though it could specify format details like SSH host strings.

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 specific action ('Get') and resource ('basic system information'), listing concrete examples of what information is retrieved (OS version, kernel, hostname, uptime). It distinguishes itself from siblings like get_cpu_info or get_memory_info by covering a broader set of system-level details rather than specific components.

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 on when to use the tool (for basic system info) and includes usage guidance in the Args section about remote vs. local execution. However, it does not explicitly state when NOT to use it or name specific alternatives among siblings for more detailed or component-specific information.

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