install_skill

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

Given no annotations, the description adequately discloses the two-step destructive behavior (preview then install) and auto-detection of agents. It explains that the first call shows a preview without installing, and confirmation is required. It does not detail error conditions or side effects like overwriting, but the core behavior is clear.

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 two sentences, front-loaded with the purpose, and provides usage guidance without any wasted words. It is appropriately sized for a simple tool.

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 mutation tool with no output schema and no annotations, the description covers the essential behavior: two-step installation, auto-detection, and parameter roles. It lacks details on what the preview returns and success confirmation, but overall it is sufficiently complete for a tool with only 3 parameters and a simple workflow.

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 baseline is 3. The description adds minimal new meaning beyond the parameter descriptions; it reiterates the flow and auto-detection, which are already implied in schema descriptions for 'confirm' and 'agents'.

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 a skill to the local filesystem, with a specific two-step process (preview then confirm). It distinguishes from sibling tools like browse_catalog or search_skills, which are read-only or information-retrieval tools.

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 explicit steps: first call for preview, then call with confirm=true to install. It mentions auto-detection of the CLI environment. However, it does not explicitly contrast with sibling tools or state when not to use this tool.

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