arch-linux-mcp

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

Annotations already declare readOnlyHint=true, indicating this is a safe read operation. The description adds useful context about what each action does (e.g., 'suggest' gets optimal mirrors from archlinux.org, 'health' checks for issues and gives recommendations), but doesn't disclose rate limits, authentication needs, or detailed behavioral traits beyond the basic operations. The description doesn't contradict annotations.

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 efficiently structured with a clear opening statement, bulleted action list, and specific examples. Every sentence adds value: the first explains the tool's consolidation purpose, the second enumerates actions, and the third provides concrete usage examples. No wasted words or redundant information.

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 (5 parameters, 4 distinct operations) and 100% schema coverage with annotations declaring read-only status, the description is mostly complete. It explains what each action does and provides usage examples. The main gap is lack of output format description (no output schema exists), but the description compensates somewhat by indicating what each action returns (e.g., 'lists configured mirrors', 'gives recommendations').

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?

Schema description coverage is 100%, so the schema already fully documents all 5 parameters. The description adds some semantic context by showing how parameters combine in examples (e.g., action='suggest' with country='US' and limit=5), but doesn't provide additional meaning beyond what the schema already specifies. This meets the baseline 3 when schema coverage is complete.

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 consolidates 4 mirror operations with specific verbs (status, test, suggest, health) and distinguishes it from siblings by focusing on mirror management rather than package installation, configuration analysis, or system diagnostics. It explicitly mentions 'smart mirror management' which differentiates it from basic mirror listing tools.

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 explicit guidance on when to use each action with clear examples: 'status' for listing configured mirrors, 'test' for testing speeds, 'suggest' for getting optimal mirrors from archlinux.org, and 'health' for full health checks. The examples demonstrate specific use cases with parameter combinations, showing clear alternatives within the tool itself.

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