Open a GDevelop project

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

The phrase 'isolated in-memory session' adds meaningful behavioral context beyond the readOnlyHint annotation by clarifying that no persistent changes are made. However, it does not describe what happens if a project is already open or the behavior on invalid files.

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, compact sentence that is immediately informative and front-loaded. Every word contributes value, with no redundant or tangential content.

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 largely complete: it states what is loaded and the session context. However, it omits information about return values or whether opening a new project replaces an existing session, which could be relevant for an agent's invocation decisions.

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 description coverage is 100% and the parameter 'projectFile' is clearly documented with path type and relativity. The description adds no additional parameter semantics beyond what the schema provides, so the baseline score of 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 specific action ('Load') and resource ('local .json GDevelop project') with a clear target ('into an isolated in-memory session'). This distinguishes it from sibling tools like create_project, save_project, or describe_native_project.

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 implies usage for loading an existing project, but does not provide explicit when-to-use guidance or mention alternatives like create_project for new projects. It lacks exclusion conditions or context about the session lifecycle.

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