Agent Skills MCP

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

Annotations indicate this is a non-read-only, non-destructive, non-idempotent, open-world operation, which the description aligns with by implying a download action that writes to disk. The description adds context about downloading to a local folder, but doesn't elaborate on potential behaviors like file system changes, error handling, or rate limits beyond what annotations provide.

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 a single, efficient sentence that directly states the tool's purpose without unnecessary words. It's front-loaded and appropriately sized for its function, making it easy to parse quickly.

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 (involving GitHub downloads and local file operations), annotations cover safety aspects, and an output schema exists, but the description lacks details on parameters, error cases, or integration with sibling tools. It's minimally adequate but has clear gaps in providing a complete operational context.

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 0%, but the description doesn't add any parameter details beyond the tool name's implication of a 'skill' and 'install'. It doesn't explain parameters like 'skill_slug', 'destination_dir', 'overwrite', or 'preserve_repo_prefix', leaving semantics unclear. With low coverage, the description fails to compensate, resulting in a baseline score.

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 action ('Download') and target ('a skill directory from GitHub into a local folder'), which is specific and understandable. However, it doesn't explicitly differentiate from sibling tools like 'github_skills_get_skill' or 'github_skills_suggest_skill_scaffold', which might involve similar GitHub skill operations but with different purposes.

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 no guidance on when to use this tool versus alternatives. It doesn't mention sibling tools like 'github_skills_get_skill' or 'github_skills_search_skills', nor does it specify prerequisites, such as needing a GitHub repository or local directory permissions, leaving usage context unclear.

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