Create Unreal Live Link bridge

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

The description adds context beyond the annotations by mentioning that the scaffold includes subject maps, an event queue, and runtime setup warnings, which are not in the structured data. However, it does not disclose details about side effects, network modifications, or external dependencies. No contradiction with annotations exists.

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, focused sentence that front-loads the core purpose and lists key features. It contains no redundant information and is well-structured.

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 complexity (11 parameters, no output schema) and the rich context of sibling tools, the description is insufficient. It lacks information on how the scaffold integrates, what the different modes do, and any operational prerequisites. The absence of parameter explanations further reduces completeness.

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?

With schema description coverage of only 18%, the description needed to compensate by explaining parameter semantics, but it does not. It mentions high-level concepts like 'subject maps' and 'event queue' that do not map to any of the 11 schema properties, leaving most parameters undocumented.

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 specific features like subject maps, event queue, and runtime setup warnings. This distinguishes it from sibling bridge tools by naming Unreal Engine and the protocols involved.

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 no guidance on when to use this tool versus alternatives. It does not list any prerequisites, exclusions, or references to other bridge creation tools, leaving the agent to infer usage from the name and description alone.

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