arch-linux-mcp

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

The description adds valuable behavioral context beyond annotations: it explains the consequences of each action ('prevent package from being removed as orphan', 'allow package to be auto-removed with orphans'), provides platform limitations, and gives concrete examples. Annotations indicate non-readonly and non-destructive operations, which the description doesn't contradict but enhances with practical implications.

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 purpose statement, action explanations, platform constraint, and concrete examples - all in four sentences. Every sentence adds value: the first establishes scope, the second explains actions, the third provides constraints, and the fourth gives practical examples. No wasted words.

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?

For a tool with 2 parameters, 100% schema coverage, and no output schema, the description provides excellent context about actions, consequences, and platform constraints. The only minor gap is lack of explicit information about return formats for the 'list' action, but the examples imply what to expect. Given the annotations cover safety aspects, this is quite complete.

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 schema already documents both parameters thoroughly. The description adds minimal value beyond the schema by providing usage examples that illustrate parameter combinations, but doesn't explain parameter semantics beyond what's in the schema descriptions. This meets the baseline for 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's purpose with specific verbs ('manage', 'list', 'mark_explicit', 'mark_dependency') and resources ('package install reasons', 'explicitly installed packages'). It distinguishes itself from siblings by focusing on package installation tracking rather than installation/removal (install_package_secure, remove_packages), orphan management (manage_orphans), or system analysis 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: 'list' for viewing user-installed packages, 'mark_explicit' to prevent orphan removal, and 'mark_dependency' to allow auto-removal. It also specifies platform constraints ('Only works on Arch Linux') and distinguishes from siblings by focusing on installation tracking rather than package operations.

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