dsh_plugin_install

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

With no annotations, the description must disclose behavioral traits. It indicates a mutation (install) and adds a safety requirement (--allow-install). However, it omits potential side effects, such as whether installation is immediate, reversible, or affects existing plugins, leaving some behavioral ambiguity.

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, focused sentence. It starts with the action, mentions the mechanism, and includes a requirement. There is no wasted wording, and it is perfectly sized for the tool's simplicity.

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 simple install tool with one parameter and no output schema, the description covers the core action and a prerequisite. However, it lacks context about post-install behavior (e.g., if the plugin is immediately available or if a runtime restart is needed), which would be useful given sibling runtime tools. It is adequate but has a clear gap.

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?

The schema fully covers the single 'spec' parameter with examples ('github:owner/repo, npm name, or path'), so the description need not add more. The description offers no additional parameter detail, but the baseline of 3 is appropriate given 100% schema coverage.

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 a plugin into the DSH profile', and identifies the underlying command 'dsh plugin add'. This distinguishes it from siblings like uninstall, list, and search, making the tool's purpose unambiguous.

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 gives the critical prerequisite 'Requires --allow-install', telling the agent when the tool can be invoked. It doesn't explicitly compare with alternatives, but for an install operation the intended usage is clear given the sibling set.

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