arch-linux-mcp

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

Annotations declare readOnlyHint=true, indicating a safe read operation. The description adds valuable behavioral context beyond annotations by specifying the scope of information retrieved (e.g., 'comprehensive system information'), the systems it works on ('any system'), and details about return values (e.g., 'Arch version, kernel, architecture'), though it doesn't cover aspects like rate limits or error handling.

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 front-loaded with the core purpose, followed by specifics on scope and returns, all in two efficient sentences with no wasted words. Every sentence adds value, such as clarifying system compatibility and output 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 the tool's low complexity (0 parameters, read-only), annotations cover safety, and the description compensates for the lack of output schema by detailing return values. It is mostly complete, though minor gaps like error scenarios or exact data formats could be addressed.

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 tool has 0 parameters, with 100% schema description coverage. The description does not need to add parameter information, so it appropriately focuses on output semantics. A baseline of 4 is applied as it compensates for the lack of output schema by detailing return values.

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 with specific verbs ('Get comprehensive system information') and resources ('kernel version, architecture, hostname, uptime, memory statistics'), distinguishing it from sibling tools like 'diagnose_system' or 'run_system_health_check' which imply deeper analysis rather than basic information retrieval.

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 by stating 'Works on any system' and listing returned data, but does not explicitly specify when to use this tool versus alternatives like 'diagnose_system' or 'run_system_health_check'. It provides some context but lacks clear exclusions or named alternatives.

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