Create Unreal Live Link bridge

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

Annotations already state readOnlyHint=false and destructiveHint=false, so the description only needs to add behavioral context. It adds that the scaffold includes subject maps, event queue, and runtime setup warnings, which is useful. However, it doesn't disclose side effects such as creating COMPs under parent_path or requiring an open world, so transparency is moderate.

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, front-loaded, information-dense sentence without fluff. Every word adds value, and it's appropriately concise for the tool's purpose.

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 tool with 11 parameters and no output schema, the description provides a high-level summary of what the scaffold includes. It lacks details about prerequisites, integration with the open world, and runtime behavior, but it is minimally adequate for a creation tool with annotations covering safety.

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 18% (name and parent_path have descriptions). The description does not explain the mode parameter (livelink_osc, udp_json, ndi_preview), port settings, sync flags, or subject_name. It vaguely alludes to subject maps but doesn't compensate for the overwhelmingly undocumented 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 it creates an Unreal Engine Live Link/OSC/NDI handoff scaffold with subject maps, event queue, and runtime setup warnings. This specific verb+resource+scope distinguishes it from sibling bridge tools like connect_unity_osc_bridge or create_synesthesia_unreal_osc.

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 implied via the description: use when you need an Unreal Engine Live Link/OSC/NDI handoff scaffold. But it doesn't explicitly state when not to use it or mention alternatives, so it lacks explicit exclusions or comparisons to other bridge tools.

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