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 mentions that the tool 'queries' logs and supports remote execution via SSH, but fails to disclose critical traits: whether this is a read-only operation, potential side effects (e.g., if it consumes system resources), authentication requirements beyond SSH username, rate limits, or error handling. The description adds some context (remote execution logic) but leaves significant gaps for a tool with 6 parameters and no annotation coverage.

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 well-structured and appropriately sized. It starts with a clear purpose statement, followed by a bullet-like 'Args' section that efficiently documents each parameter. Every sentence earns its place by providing essential information, though the SSH-related details could be slightly more concise. No redundant or verbose content is present.

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 complexity (6 parameters, no annotations, but with an output schema), the description is reasonably complete. It thoroughly documents all input parameters and their semantics. Since an output schema exists, the description doesn't need to explain return values. However, it lacks behavioral context (e.g., safety, limitations) which would be beneficial despite the output schema.

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 provides comprehensive parameter semantics beyond the input schema, which has 0% description coverage. For all 6 parameters, it explains their purpose, constraints (e.g., 'default: 100' for lines, priority enum values, SSH dependency rules), and usage examples (e.g., time formats for 'since'). This fully compensates for the lack of schema descriptions, adding significant value for agent understanding.

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: 'Query systemd journal logs with optional filters.' This specifies the verb ('query') and resource ('systemd journal logs'), making it distinct from sibling tools like 'get_service_logs' or 'read_log_file' which handle different log sources. However, it doesn't explicitly differentiate from 'get_audit_logs' which might also query logs but from a different subsystem.

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 context through parameter explanations (e.g., 'optional filters,' 'executes locally if not provided'), but lacks explicit guidance on when to use this tool versus alternatives like 'get_service_logs' or 'read_log_file.' It mentions remote execution via SSH but doesn't specify prerequisites or when remote vs local is appropriate beyond parameter requirements.

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