Stage Object Deselect

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

No annotations are provided, so the description carries the behavioral burden. It discloses meaningful side effects: in VR it closes the action menu and locks again a thing unlocked with Move, it reports {selected: null}, and it emits deselect and panel_closed events conditionally. It does not cover permissions or error behavior, but it is substantially transparent for a state-clearing tool.

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 compact, front-loaded with the core action, and each sentence adds useful behavioral detail. There is no wasted text or irrelevant repetition.

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?

An output schema exists, so the description need not fully explain return values, and it does mention the page reply. However, the single required parameter remains completely undescribed, which is a material gap for an agent trying to invoke the tool correctly. Behavioral side effects are otherwise well covered.

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?

There is one required parameter, 'scene', with 0% schema description coverage. The description never explains what 'scene' means, what format it expects, or whether it is a scene name or identifier. The only parameter is therefore undocumented in both schema and prose.

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: 'Clear the selection', and it names the page command. It is clearly distinguishable from the sibling stage_object_select tool by describing the inverse operation. An agent can tell what it does without opening the schema.

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 purpose implies when to use it (when a selection should be cleared), and the VR side effects are described. However, it does not explicitly compare with alternatives such as stage_object_select, stage_panel_close, or stage_grab_mode. Usage is implied rather than routed.

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