arch-mcp

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

The description adds valuable behavioral context beyond the 'destructiveHint: true' annotation, detailing the multi-step security workflow (e.g., checking repos, analyzing trust scores, blocking on critical issues) and prerequisites like sudo and AUR helpers. It does not contradict the annotation, as installation is inherently destructive.

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 well-structured with a numbered workflow and clear prerequisites, but it could be more front-loaded; the first sentence captures the essence, but the detailed steps might be verbose for a quick scan. Every sentence adds value, avoiding waste.

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 complexity (security workflow, prerequisites) and lack of output schema, the description is fairly complete, covering behavior, constraints, and usage context. However, it could specify error handling or output format more explicitly for full completeness.

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 already documents the 'package_name' parameter. The description adds minimal semantics by mentioning it checks 'official repos first, then AUR', but this is implied in the workflow steps, not detailed parameter behavior.

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 specific action ('Install a package with comprehensive security checks') and distinguishes it from siblings like 'remove_packages' or 'audit_package_security' by focusing on installation with security workflows. It specifies the resource (package) and verb (install) with added security context.

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?

Explicit guidelines are provided: 'Only works on Arch Linux', 'Requires sudo access and paru/yay for AUR packages', and details when to use (e.g., for AUR packages with trust analysis). It implicitly contrasts with simpler installation tools by emphasizing security checks.

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