Create OptiTrack tracking bus

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

The annotations already indicate this is a creation (readOnlyHint=false) with open-world side effects (openWorldHint=true) and non-destructive (destructiveHint=false). The description adds useful context that it creates a 'scaffold' with specific internal components, implying a starting template rather than a fully configured system. However, it does not disclose details like whether an existing component is required, connection prerequisites, or what happens on repeated calls.

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 of 17 words. It front-loads the action and resource, and avoids any filler or redundant wording. Every phrase adds value.

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 8 parameters, no output schema, and minimal parameter documentation, the description is insufficient for an agent to fully understand the tool's behavior. It does not explain what the tool returns (e.g., the created scaffold), how parameters map to the receiver/rigid-body/marker setup, or any preconditions. The high-level scaffold concept is clear, but the operational details are missing.

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 25% (only name and parent_path have descriptions). The description does not explicitly explain any of the parameters such as data_port, command_port, marker_count, server_address, or rigid_body_count. While the components (receiver, maps) loosely map to these parameters, the description fails to compensate for the low schema coverage by relating them.

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 the specific verb ('Create') and resource ('OptiTrack/NatNet tracking scaffold'), and differentiates from sibling tracking tools by naming OptiTrack/NatNet and listing the scaffold components (receiver, rigid-body maps, marker maps, calibration notes). This is a specific and distinctive purpose.

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?

No guidance is provided on when to use this tool versus alternatives. The description does not mention when to choose this over other tracking bus tools (e.g., create_blacktrax_tracking_bus) or any prerequisites such as needing a running NatNet server or an existing parent component.

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