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. The description mentions SSH connectivity for remote execution, which is useful context. However, it doesn't disclose important behavioral traits like whether this requires specific permissions, what format the output takes, whether it's a read-only operation, potential rate limits, or error conditions. For a tool with zero annotation coverage, this is a significant gap.

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: the first sentence states the core purpose, followed by parameter documentation. There's no wasted text. However, the parameter documentation could be slightly more structured (e.g., using bullet points), and the description could benefit from a clearer separation between the purpose statement and parameter details.

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 handles return values) and no annotations, the description provides adequate basic information about what the tool does and its parameters. However, for a tool that executes commands (potentially via SSH), it should ideally mention security implications, permission requirements, or execution context more explicitly. The description is complete enough for basic understanding but lacks depth for a tool with potential operational complexity.

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 provides meaningful semantics for both parameters: 'host' is described 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 context beyond the bare schema, explaining the relationship between parameters and the local/remote execution behavior. However, it doesn't cover all potential parameter details like format requirements or examples.

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 network interface information including IP addresses.' This is a specific verb ('Get') + resource ('network interface information') combination that distinguishes it from siblings like get_network_connections (which focuses on connections rather than interfaces). However, it doesn't explicitly differentiate from all siblings, 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 provides implied usage guidance through the parameter documentation: it explains when 'host' is optional (executes locally if not provided) and when 'username' is required (if host is provided). However, it doesn't explicitly state when to use this tool versus alternatives like get_network_connections or get_system_info, nor does it provide any exclusions or prerequisites 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.