plugin_install

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

Annotations are readOnlyHint=false and destructiveHint=false. Description explains non-interactive permission grants and the installation process. Could mention idempotency or overwrite behavior, but overall 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?

Well-structured with front-loaded purpose, then details, then parameter descriptions, and return info. A bit lengthy but no unnecessary words.

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?

Covers installation flow, parameter semantics, return type (dict), and related tools. No output schema but description compensates. Lacks edge cases like error handling.

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?

With 0% schema description coverage, the description fully explains both parameters: remote is a Docker Hub reference in 'author/name:tag' form, and local_name is an alias defaulting to remote. Provides example format.

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 plugin from Docker Hub, specifying the remote format and using verbs like 'install'. It distinguishes from sibling tools like plugin_list, plugin_enable, plugin_configure, etc.

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?

Provides explicit guidance on when to use this tool (install from Docker Hub) and subsequent steps: use plugin_inspect, then plugin_enable or plugin_configure. Mentions alternatives like plugin_list and plugin_remove.

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