リアルタイム制御ブリッジプラグインのインストール

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

With no annotations provided, the description carries the full burden. It reveals the install location, the mechanism (named pipe), the effect (real-time control), the need for a restart, and the non-overwrite guarantee due to an independent file name. This is strong behavioral disclosure for a file-install operation, though it omits potential permission requirements or error conditions.

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?

The description is four sentences, all substantive. It front-loads the primary action (install) and then adds necessary context about the effect, restart requirement, and safety guarantee. No fluff or redundancy.

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?

Given the tool's simplicity (one parameter, no output schema), the description covers essential aspects: purpose, path, effect, restart, and non-overwrite. It could additionally mention admin privileges or what happens if already installed, but these are not critical for an install tool with a boolean overwrite flag.

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, 'overwrite', is fully described in the schema (100% coverage) as a boolean with default true. The description does not add extra meaning beyond the schema, which is acceptable given the baseline of 3 for self-explanatory parameters.

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 bundled native plugin (mcp_bridge.dll) to a specific path (C:\ProgramData\aviutl2/Plugin/aviutl2-mcp-bridge.aux2). It explicitly ties this to enabling live_* tools, distinguishing it from sibling tools like install_script and uninstall_script.

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?

The description provides clear usage context by stating the installation enables real-time control of AviUtl2 via named pipes for live_* tools and that a restart is required. It does not explicitly state when not to use it or name alternatives, but the purpose is clear enough for an install action.

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