Stage Object Select

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

With no annotations provided, the description carries the burden well: it discloses the VR panel side effect, event emissions, and the page reply shape. It does not cover error behavior, permissions, or whether selecting a new object replaces the previous selection.

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 dense but front-loaded, moving from purpose to VR behavior to return/event details. Most sentences earn their place, though the actions.js reference and event list make it slightly heavier than necessary.

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?

It gives a strong behavioral picture and includes return/event details, but with zero schema description coverage and no annotations, it leaves important invocation details unclear: the scene parameter, object value format, and the relationship to stage_object_deselect.

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 0%, so the description must compensate for both parameters. It explains that object=None clears the selection, but it does not explain what object values look like or what the required scene parameter means.

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 states a specific verb and resource: selecting an object, with the special case of clearing selection when object is None. It is clear enough to distinguish from most siblings, though it does not explicitly differentiate this from stage_object_deselect.

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?

It implies usage by explaining that object=None clears the selection and that selecting a movable object in VR opens its action menu. It does not explicitly say when to prefer this over stage_object_deselect or other stage-object siblings, leaving the overlap for the agent to infer.

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