Linux MCP Server

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

The description adds minimal behavioral context beyond what annotations provide. The annotation 'readOnlyHint: true' already indicates this is a safe read operation. The description doesn't disclose any additional behavioral traits like whether this requires elevated permissions, how it handles remote hosts (via SSH), what the output format looks like, or any rate limits. However, it doesn't contradict the annotation either.

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 concise at just 4 words. It's front-loaded with the essential information (what the tool does) with zero wasted words. Every word earns its place by specifying both the action and the exact type of resource being retrieved.

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 this tool has rich annotations (readOnlyHint), a comprehensive input schema with 100% coverage, and an output schema (though not shown), the description is minimally adequate. However, for a tool with 6 parameters that can query remote systems via SSH, the description could provide more context about typical use cases, limitations, or how it differs from sibling logging tools. The existence of an output schema means the description doesn't need to explain return values.

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 100% schema description coverage, the schema already documents all 6 parameters thoroughly with descriptions, examples, and defaults. The description adds no additional parameter semantics beyond what's in the schema. It doesn't explain relationships between parameters, provide usage examples, or clarify edge cases. The baseline of 3 is appropriate when the schema does all the heavy lifting.

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 verb 'Get' and resource 'systemd journal logs', making the purpose immediately understandable. However, it doesn't distinguish this tool from sibling tools like 'get_service_logs' or 'read_log_file', which also retrieve logs but from different sources. The description is specific about what type of logs it retrieves but doesn't clarify how it differs from similar logging tools.

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 no guidance on when to use this tool versus alternatives. There's no mention of when to prefer this over 'get_service_logs' (which might retrieve logs for specific services) or 'read_log_file' (which reads arbitrary log files). No context about prerequisites, typical use cases, or limitations is provided.

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