arch-linux-mcp

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

Annotations indicate readOnlyHint=true, which the description aligns with by describing a diagnostic/checking operation ('run a comprehensive system health check') rather than a write action. The description adds useful context beyond annotations by specifying the OS constraint ('Only works on Arch Linux') and listing the types of diagnostics performed, but does not detail behavioral aspects like execution time, output format, or potential side effects.

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 in the first sentence and efficiently lists key diagnostics in subsequent sentences. It avoids redundancy and stays focused on essential information, though it could be slightly more streamlined by combining some details into a single list.

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 (comprehensive health check) and the absence of an output schema, the description does a good job of explaining what the tool does, its OS constraint, and the diagnostics included. However, it could improve by hinting at the output structure or format, as the agent might need to know what to expect from the results.

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 input schema has 0 parameters with 100% description coverage, so no parameter documentation is needed. The description appropriately does not discuss parameters, focusing instead on the tool's functionality and scope. This meets the baseline for tools with no parameters, as it avoids unnecessary details.

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 ('run', 'integrates', 'provide') and resources ('system health check', 'multiple diagnostics', 'complete overview of system status'). It explicitly distinguishes itself from siblings by being comprehensive and covering multiple areas (disk space, failed services, updates, orphan packages, etc.), unlike more focused sibling tools like check_database_freshness or analyze_storage.

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 clear context for when to use this tool: for a 'comprehensive' health check on 'Arch Linux' systems. It implies usage by listing the specific diagnostics included (updates, disk space, etc.), but does not explicitly state when not to use it or name alternatives among the siblings, such as using diagnose_system for a different scope or get_system_info for less detail.

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