skillNinja_install

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

With no annotations, the description carries full burden. It discloses the conditional behavior (resolvable source vs stub) and that AGENTS.md is updated, but does not mention potential overwrites, authorization requirements, or error handling.

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 concise with two English sentences and a Japanese translation. It is front-loaded with the core purpose, though the Japanese section could be considered redundant for an English-language system.

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 output schema and moderate complexity, the description covers the main action and conditional behavior adequately. It is mostly complete, though missing details on failure modes or workspace path validation.

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 coverage is 100%, so baseline is 3. The description adds limited value beyond schema, only implicitly linking 'source' to content resolvability without clarifying disambiguation logic.

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 installs an Agent Skill to the workspace, with specific actions (downloading SKILL.md or generating a stub and updating AGENTS.md). It distinguishes from sibling tools like uninstall and list.

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 context on behavior (conditional download vs stub generation) but does not explicitly state when to use this tool versus alternatives like skillNinja_addSource or skillNinja_search.

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