unity_scene_open

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

No annotations are provided, so the description must disclose behavioral traits. It only states 'Open a scene' without explaining what happens to the current scene, whether unsaved changes are lost, or if compilation occurs. This is insufficient for an AI agent to anticipate side effects.

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 concise sentence that front-loads the action and resource. It could be slightly improved by adding one more sentence about side effects, but it remains efficient and to the point.

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?

Given the tool has 2 parameters, no output schema, and no annotations, the description adequately covers how to specify the scene path. However, it omits important context about the effect on the current scene, error handling, and when to prefer this over other scene tools.

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%, so the baseline is 3. The description adds value by clarifying that the path is relative to 'Assets/', which is not in the schema's type definition. However, it does not mention the 'port' parameter, leaving that solely to 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 action ('Open a scene') and the unique method of specifying it ('by its asset path relative to Assets/'). This distinguishes it from sibling tools like unity_scene_new (creates new) and unity_scene_save (saves).

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 lacks any guidance on when to use this tool versus alternatives (e.g., unity_scene_new or unity_scene_save). It does not mention prerequisites (scene must exist) or potential side effects (closing current scene without saving). The only usage hint comes from the schema's port parameter description, not the tool description itself.

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