arch-linux-mcp

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

The description adds valuable behavioral context beyond the readOnlyHint annotation, such as the OS limitation ('Only works on Arch Linux'), the specific scenarios for use ('After system crash or disk errors'), and the types of issues detected ('modified, missing, or corrupted files'). It does not contradict the readOnlyHint (which indicates safe read operations) and provides practical insights into the tool's behavior and constraints.

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 main purpose in the first sentence, followed by usage guidelines, all in two efficient sentences with no wasted words. Every sentence adds critical information (e.g., OS limitation, use cases), making it appropriately sized and well-structured for quick understanding.

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 moderate complexity (2 parameters, read-only operation), the description is mostly complete, covering purpose, usage, and behavioral context. However, without an output schema, it lacks details on return values (e.g., what the verification results look like), leaving a minor gap in full contextual understanding for an agent invoking the tool.

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 input schema fully documents both parameters ('package_name' and 'thorough'). The description does not add any parameter-specific details beyond what the schema provides, such as examples or edge cases, so it meets the baseline for high schema coverage without compensating with extra semantic information.

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 ('verify integrity', 'detects modified, missing, or corrupted files') and resource ('installed package files'), distinguishing it from siblings like 'audit_package_security' or 'run_system_health_check' by focusing on file-level integrity verification rather than security or broader system checks.

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 explicitly states when to use this tool ('After system crash or disk errors') and provides context ('verify package files match expected checksums'), with no misleading or vague guidance. It clearly differentiates from siblings by specifying its maintenance role and OS limitation ('Only works on Arch Linux').

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