agent-skill-loader

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

With no annotations provided, the description carries full burden. It discloses key behavioral traits: copying entire directories, default destination path, and security constraint (must be within current working directory). However, it doesn't mention error conditions, permission requirements, or what happens if the skill already 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?

Two sentences with zero waste. First sentence states the core action and scope, second sentence provides default behavior and security constraint. Every element serves a clear purpose without redundancy.

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 no annotations and no output schema, the description covers the basic operation well but lacks information about return values, error handling, or what constitutes a successful installation. It's adequate for understanding what the tool does but incomplete for full 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 100%, so the schema already documents both parameters well. The description adds value by explaining the default behavior (target_path defaults to .agent/skills/<skill_name>) and security constraint, providing context beyond the schema's parameter descriptions.

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 ('Copies an entire skill directory') and resource ('skill directory including SKILL.md and supporting files'), with explicit destination details. It distinguishes from siblings like 'list_skills' (listing) and 'read_skill' (reading) by focusing on installation/copying.

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 context through the default installation path and security constraint, but doesn't explicitly state when to use this tool versus alternatives like 'manage_search_paths' or prerequisites. It provides operational context but lacks comparative guidance.

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