install_plugin

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

No annotations provided, so description must cover behavior. It mentions installation necessity but fails to disclose side effects (e.g., overwrite behavior), permissions (e.g., network access for store/url), or idempotency. Agent lacks details on what happens if plugin already installed or if dependencies are required.

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?

Two sentences, no wasted words. First sentence covers all parameters and methods; second provides usage context. Information is front-loaded.

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?

With no output schema, description should explain outcomes. It mentions pre-condition (needed before using plugin formats) but not post-condition or return value. Adequate for a simple installer but lacks return info or error handling hints.

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%, baseline 3. Description adds value by explaining that 'id' is a store plugin id with example, 'url' is direct https to .js, and 'path' is local file path. Clarifies alternative methods beyond schema's generic 'Store plugin id.' description.

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?

Explicitly states the action (install), the resource (plugin), and the three methods (id, url, path). Distinguishes from sibling tools like uninstall_plugin and list_plugins.

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 clear context: 'Needed before using plugin-specific formats like GeckoLib's geckolib_model.' Does not explicitly exclude cases or mention alternatives, but the trigger scenario is well-defined.

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