set_render_mode

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

Annotations indicate destructive mutation (readOnlyHint=false). The description adds context by explaining each rendering mode's visual behavior, but does not disclose side effects on occlusion, background, or other settings when changing modes.

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 short and front-loaded with the core purpose. It is efficient with no filler, though it could be slightly more structured (e.g., bullet points) for readability.

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 6 parameters (1 required), the description covers only the mode parameter. The interplay of occlusionMode, backgroundType, etc., is not explained. Schema covers definitions, but behavioral interactions are missing, leaving gaps for an agent.

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 good enum descriptions. The description adds no new parameter details beyond the main 'mode' enumeration; it merely restates what the schema already provides. Baseline 3 is appropriate.

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 rendering mode for XREAL and briefly explains VR, AR, MR. It distinguishes the main function from sibling tools like configure_passthrough or set_tracking_mode, but does not explicitly differentiate itself beyond the mode focus.

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 vs alternatives, nor any prerequisites or exclusions. It only states the modes, leaving the agent to infer context from sibling names.

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