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 listing read-only actions (list_groups, list_packages_in_group). The description adds context about the two specific operations and provides examples, but doesn't disclose additional behavioral traits like rate limits, error handling, or data formats beyond what annotations cover. No contradiction with annotations exists.

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 appropriately sized with three sentences: a purpose statement, action listing, and examples. It's front-loaded with the main purpose and avoids unnecessary details. However, the examples could be more integrated into the flow rather than appended, and some wording like '[ORGANIZATION]' is placeholder-like.

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 actions) and lack of output schema, the description is minimally complete. It covers the actions and provides examples, but doesn't explain return values, error cases, or how results are structured. With annotations covering safety, it's adequate but leaves gaps for an agent to infer behavior fully.

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%, with clear documentation of the 'action' enum and 'group_name' parameter. The description adds minimal value by mentioning the actions in prose and providing examples that illustrate parameter usage, but doesn't elaborate on semantics beyond what the schema already specifies. Baseline score of 3 is appropriate given high schema coverage.

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 performs unified group management with two specific actions: listing all groups and listing packages in a specific group. It provides a verb+resource combination ('manage groups') and distinguishes between the two actions, though it doesn't explicitly differentiate from sibling tools like 'manage_orphans' or 'query_package_history' which might have overlapping domains.

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 through the examples provided (e.g., manage_groups(action='list_groups')), which suggests when to use each action based on the 'action' parameter. However, it lacks explicit guidance on when to choose this tool over alternatives like 'query_package_history' or 'search_aur' for related tasks, and doesn't mention prerequisites or exclusions.

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