installBridge

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

With no annotations at all, the description carries the full burden, and it does disclose real side effects: it scans for AE installations, writes a .jsx file into the ScriptUI Panels directory, and performs automatic menu backup cleanup. It omits whether an existing install is overwritten, idempotency, required file permissions, and whether a restart is needed — significant gaps for a filesystem-mutating 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?

One sentence, front-loaded with the core action, with the backup-cleanup caveat tucked into a parenthetical rather than buried mid-sentence. Dense but no wasted clauses.

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?

No output schema exists, so the description should say what comes back (e.g. which installations were detected, whether installation succeeded) and whether AE must be relaunched; it says none of that. For a one-parameter setup tool it is adequate but leaves real operational questions unanswered.

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?

There is a single optional parameter with 100% schema description coverage ('Optional custom ScriptUI Panels directory path'), so the schema already does the work. The description adds the useful implication that the directory is auto-detected by default, but gives no format or example for the override.

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 states a specific verb (install) and resource (the mcp-bridge-auto.jsx panel script placed into ScriptUI Panels), plus the auto-detection step. It partially separates itself from siblings like cleanBridgeBackups by mentioning built-in menu backup cleanup, though it never names those siblings 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?

Usage is only implied: an agent can infer this is the setup step that must precede the bridge-dependent tools. There is no explicit 'use when' statement, no mention of prerequisites (e.g. whether After Effects must be closed or restarted), and no pointer to cleanBridgeBackups or rollback as alternatives.

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