setup_xr_interaction

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

The description implies state changes (installation, configuration) matching the readOnlyHint=false annotation. However, it does not detail potential side effects like overwriting existing configurations or dependency requirements.

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?

Two sentences, clear and free of fluff. Could benefit from bullet points but remains efficient.

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?

Does not explain return values, success indicators, or expected outcomes. Missing context about how this tool relates to sibling tools like setup_xreal_project or enable_hand_tracking.

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 coverage is 100% with each parameter described. The tool's description adds no further insight into parameter usage or relationships beyond the schema.

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 tool sets up the XR Interaction Toolkit and configures interaction systems, input actions, and interactors. It is specific about the resource and actions, though it does not explicitly differentiate from sibling tools like configure_hand_gestures.

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 on when to use this tool versus alternatives, such as configure_hand_gestures or enable_hand_tracking. No prerequisites or context about the setup order are provided.

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