Linux MCP Server

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

With no annotations provided, the description carries full burden for behavioral disclosure. It mentions that logs are retrieved 'if available' which hints at conditional availability, but doesn't explain what determines availability, error conditions, or authentication requirements. The SSH execution context is mentioned in parameter descriptions but not in the main behavioral description. No information about rate limits, permissions needed, or what happens when host/username are omitted.

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 well-structured. The first sentence states the purpose, followed by clear parameter explanations in a bullet-like format. Each parameter description earns its place by adding meaningful context. No redundant information or unnecessary elaboration.

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 has 3 parameters, no annotations, but has an output schema, the description is moderately complete. The parameter explanations are strong, but the behavioral context is lacking. The existence of an output schema means the description doesn't need to explain return values, but it should provide more context about the tool's operation, error conditions, and relationship to sibling tools.

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 excellent parameter semantics that go well beyond the input schema. With 0% schema description coverage, the description fully compensates by explaining: 'lines' controls the number of log lines retrieved with a default, 'host' enables remote SSH execution with local fallback, and 'username' is conditionally required. This adds crucial context about how parameters interact that isn't in the schema.

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 states the tool 'Get audit logs if available' which provides a basic verb+resource combination, but it's vague about what 'audit logs' specifically refer to and doesn't distinguish this from sibling tools like 'get_journal_logs' or 'get_service_logs'. It doesn't specify the source or type of audit logs being retrieved.

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. It doesn't mention sibling tools like 'get_journal_logs' or 'get_service_logs' that might serve similar purposes, nor does it explain when audit logs would be preferred over other log types. There's no context about prerequisites or typical use cases.

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