skillNinja_install

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

With no annotations provided, the description carries full burden. It mentions downloading and updating files, which implies mutation and potential side effects, but doesn't disclose critical behavioral traits like required permissions, whether it overwrites existing files, error handling, or confirmation prompts. This is inadequate for a mutation tool with zero annotation coverage.

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 front-loaded with the main action and files affected, followed by a Japanese translation that adds no functional value. The first sentence is efficient, but the second sentence is redundant for an AI agent, slightly reducing conciseness.

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 no annotations, no output schema, and a mutation tool with two parameters, the description is incomplete. It lacks details on behavioral aspects (e.g., what happens on success/failure, side effects), and doesn't compensate for the absence of structured data, making it insufficient for safe and effective use.

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 ('skillName' and 'workspacePath'). The description adds no additional meaning about parameters beyond what the schema provides, such as format examples or constraints. Baseline 3 is appropriate when schema does the heavy lifting.

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 ('Install') and target ('Agent Skill to the workspace'), with specific details about what files are affected (SKILL.md and AGENTS.md). It distinguishes from siblings like 'uninstall' and 'updateIndex' by focusing on installation. However, it doesn't explicitly differentiate from 'addSource' which might also involve adding skills.

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?

No explicit guidance on when to use this tool versus alternatives like 'addSource' or 'localize'. The description implies installation but doesn't specify prerequisites (e.g., whether the skill must be available in a repository) or when not to use it (e.g., if already installed).

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