Connect Runway video bridge

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

Annotations already cover readOnlyHint=false and destructiveHint=false, so the creation behavior aligns. The description adds context about scaffold components (prompt maps, contracts, polling status, adapter notes) but does not disclose potential side effects, external dependencies, or whether it overwrites existing content.

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 a single sentence with no filler, front-loading the main action and then listing deliverables. It is dense but somewhat jargon-heavy ('handoff scaffold'), though still concise.

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 9 parameters, no required params, no output schema, and low schema coverage, the description is too sparse to convey the full scope. It does not explain return values, setup prerequisites, or how the scaffold is connected or used after creation, leaving significant gaps for a tool of this complexity.

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 description coverage is only 22%, and the description does not elaborate on any of the 9 parameters. It mentions high-level scaffold components but no mapping to specific parameters like endpoint_url, prompt_count, or generation_mode. The description fails to compensate for the low schema coverage.

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 it creates a Runway-style video generation handoff scaffold, with specific components listed. The verb 'Create' is specific, though the tool name says 'connect' which creates minor ambiguity. It does distinguish from sibling bridge tools by the Runway-specific context.

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?

There is no explicit guidance on when to use this tool versus alternatives such as connect_replicate_prediction_bridge or connect_comfyui. The description only states what it does, not when it should be preferred, nor any prerequisites or exclusions.

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