open_scene

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

Minimal disclosure: 'Open' does not explain whether it loads into the editor, makes it active, or what side effects occur. No annotations provided, so the description carries full burden but fails to describe key behaviors like error handling or permissions.

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?

Extremely concise: one sentence, no redundancy. Every word is useful, and the structure is front-loaded with the verb and resource.

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?

For a simple tool with one parameter, the description is adequate but not complete. It lacks details such as what 'open' means operationally (e.g., does it replace the current scene?), error conditions, or output. Without an output schema, more explanation would be helpful.

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?

With 0% schema description coverage, the description adds value by specifying the path format ('res:// path'), which helps the agent format the parameter. However, it does not elaborate on allowed values or constraints beyond that.

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') and resource ('Godot scene') along with the specific path type ('res:// path'), making the tool's purpose unambiguous and distinguishable from siblings like 'create_scene' or 'play_current_scene'.

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 (e.g., 'load_resource', 'instantiate_scene'). The description does not mention prerequisites or conditions, leaving the agent to infer the usage context.

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