arch-mcp

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

Annotations provide readOnlyHint=true, indicating a safe read operation. The description adds context beyond annotations by specifying the return values (CFLAGS, MAKEFLAGS, etc.) and the OS constraint (Arch Linux), which is useful behavioral information. However, it doesn't detail potential errors, file location assumptions, or output format, leaving some behavioral aspects unclear despite the annotation coverage.

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 concise with two sentences, but it's somewhat repetitive (e.g., 'Returns CFLAGS...' is stated twice). The information is front-loaded with the core action, but the repetition reduces efficiency. It could be more structured by combining the return details into a single, non-redundant statement.

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 no parameters, annotations cover read-only safety, and no output schema exists, the description provides basic completeness by stating what it does and OS constraints. However, it lacks details on output format, error handling, or how it locates makepkg.conf, which would be helpful for a tool with no structured output documentation.

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% coverage, so no parameter documentation is needed. The description appropriately doesn't discuss parameters, focusing instead on the tool's function and constraints. This meets the baseline for zero parameters, as it doesn't add unnecessary param info but also doesn't compensate for any gaps.

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: 'Parse and analyze makepkg.conf' and specifies what it returns (CFLAGS, MAKEFLAGS, compression settings, build configuration). It distinguishes from siblings by focusing on makepkg.conf analysis, unlike tools like analyze_pacman_conf or get_system_info. However, it doesn't explicitly differentiate from all siblings in terms of verb+resource specificity beyond the obvious filename focus.

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 some usage context by stating 'Only works on Arch Linux,' which implies when to use it (on Arch systems) and when not to use it (on other OSes). However, it doesn't offer explicit alternatives or compare with similar tools like analyze_pacman_conf for configuration analysis, leaving the agent to infer usage based on the filename target alone.

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