Create mocap stream bridge

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

Annotations already indicate a non-read-only, open-world, non-destructive operation. The description adds no behavioral context beyond the act of creation, such as side effects on the existing network graph, whether existing operators at parent_path are modified, or any prerequisites. This leaves the agent without important operational context.

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 that is front-loaded with the primary action and object. It uses no filler words and is appropriately concise for the tool's straightforward creation 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?

Given nine parameters, minimal schema descriptions, and no output schema, the description is too sparse to support correct invocation. It omits usage context, parameter semantics, return behavior, and any prerequisites or side effects, making it insufficient for a tool with 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%, so the description must compensate for undocumented parameters. It does not explain any parameters explicitly; it only vaguely refers to 'joint and rigid-body mapping surfaces', which hints at skeleton_count and rigid_body_count but does not clarify their meaning or relationships. The low-coverage schema and lack of parameter explanations leave a significant gap.

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 uses a specific verb 'Create' and identifies a precise resource: a generic OptiTrack/Rokoko/Axis Studio/VRPN-style mocap bus scaffold with joint and rigid-body mapping surfaces. This clearly differentiates it from sibling tools that target specific vendors like create_optitrack_tracking_bus or connect_xsens_mvn_mocap.

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 mention vendor-specific bridges or any criteria for selecting the generic scaffold over specific ones, leaving the agent to infer usage from sibling names.

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