streamdeck_install_mcp_plugin

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

Describes idempotency (returns installed=false unless force=true) and the plugin's purpose (encoder support for touchstrip persistence). With no annotations, the description covers key behavioral aspects, though missing error handling details.

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?

Four concise sentences: action, rationale, behavior, usage note. No fluff, each sentence adds essential information.

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 optional parameter and no output schema, the description is complete. Covers purpose, idempotency, force usage, and alternative auto-install mechanism.

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 only parameter 'force' is well-described in both schema (100% coverage) and description. Description adds context: 'Reinstall even if it already exists. Useful after upgrading streamdeck-mcp.' This adds value beyond schema.

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 specifies the action (install), the target (bundled streamdeck-mcp plugin into Elgato Plugins directory), and the reason (encoder support for persistence). It distinguishes from siblings by noting that streamdeck_write_page auto-installs, so most callers don't need this tool.

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 states when to use (force=true for reinstallation after upgrade) and when not to use (most callers don't need it because auto-install happens). Provides clear context for the tool's role.

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