streamdeck_install_mcp_plugin

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

No annotations provided, so description carries full burden. Discloses idempotency, return value when already present (installed=false), and effect of force=true. Could add more detail on permissions or side effects, but current level is good for a single-parameter tool.

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?

Three concise sentences. First sentence states main action, second explains why the plugin exists, third covers idempotency and auto-install. Every sentence earns its place, no fluff.

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 one optional parameter, no output schema, and clear sibling context, the description fully covers purpose, behavior, idempotency, and usage guidance. No missing information for an agent to use this tool correctly.

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% and schema describes force. Description adds value by explaining that force=true is useful after upgrading, which goes beyond the schema description. No other parameters to document.

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?

Clearly states the verb 'install' and specific resource 'streamdeck-mcp Stream Deck plugin' into the Elgato Plugins directory. Distinguishes from siblings by explaining that streamdeck_write_page auto-installs it, so most callers don't need this tool directly.

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 context on when to use (installing the plugin) and when not (most callers should rely on auto-install from streamdeck_write_page). Mentions force parameter for reinstalling after upgrade. Does not name a specific alternative tool explicitly, but the auto-install note serves as guidance.

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