install_plugin

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

Discloses that daemon handles permission grants non-interactively. Annotations only give readOnlyHint=false and destructiveHint=false, so description adds useful behavioral context beyond annotations.

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?

Concise yet informative. Includes code-block style for args and returns. Front-loaded with main purpose and usage flow.

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 details, return type (dict of attrs). No output schema, but the description provides reasonable insight. Given simple tool, complete enough.

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 0%, but description fully compensates by explaining remote_name format (Docker Hub reference with author/name:tag) and local_name purpose and default. Adds meaning beyond schema types.

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?

Clear verb 'install' and resource 'plugin' specified. Distinguishes from siblings like enable_plugin, configure_plugin, remove_plugin. Provides parameter format example for remote_name.

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?

Explicitly guides after installation: use get_plugin to confirm, then enable_plugin if needed, optionally configure_plugin first. Mentions related commands for listing and removing, establishing when to use alternatives.

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