arch-linux-mcp

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

The description adds valuable behavioral context beyond the readOnlyHint annotation. It specifies the tool performs 'comprehensive security audit' with two distinct action types and their scopes (50+ red flags, trustworthiness evaluation), which helps the agent understand what the audit entails. However, it doesn't mention rate limits, authentication needs, or detailed output format.

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: it starts with the core purpose, lists specific actions with details, provides clear examples, and ends with a usage guideline. Every sentence adds value without redundancy, and it's front-loaded with essential 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 complexity (security audit with multiple actions), the description is mostly complete. It explains the purpose, actions, and usage context well. However, without an output schema, it doesn't describe return values (e.g., audit results format), leaving a minor gap. The annotations (readOnlyHint) and schema coverage help compensate.

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 all parameters well. The description adds minimal value by providing examples (e.g., action='pkgbuild_analysis', pkgbuild_content='...') that illustrate parameter usage but doesn't explain semantics beyond what the schema provides. The baseline 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 a 'comprehensive security audit for AUR packages' with specific actions (pkgbuild_analysis scanning for 50+ red flags, metadata_risk evaluating trustworthiness via votes/maintainer/age). It distinguishes from siblings like install_package_secure or verify_package_integrity by focusing on pre-installation security assessment rather than installation or integrity verification.

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 explicitly states '⚠️ Always audit AUR packages before installing,' providing clear when-to-use guidance. It distinguishes from siblings by focusing on security auditing rather than configuration analysis (e.g., analyze_makepkg_conf), package management (e.g., install_package_secure), or system diagnostics (e.g., diagnose_system).

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