Create a GDevelop project

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

The description discloses that the tool creates a file and keeps it open as a session, which is behavioral information beyond the annotations (readOnlyHint=false, openWorldHint=false, destructiveHint=false). It does not mention overwrite behavior or lifecycle details, but the session disclosure adds meaningful context.

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, front-loaded sentence with no wasted words. It efficiently communicates the core action and the session behavior without padding.

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's complexity (14 parameters, no output schema, and a sizable sibling list), the description is too minimal. It does not explain key behaviors like overwrite semantics, session lifecycle, or the purpose of less obvious parameters, leaving the agent under-informed for correct invocation.

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?

The input schema has 14 parameters with 0% description coverage, and the description adds no meaning for any of them. Parameter names like loadingMinDuration and sizeOnStartupMode are not self-evident, and the description fails to compensate for the lack of schema documentation.

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 ('Create') and the resource ('a new editable GDevelop project JSON file'), and adds a distinctive behavioral trait ('keep it open as a session') that differentiates it from siblings like open_project and update_project. This is a specific and unambiguous purpose.

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 clearly implies when to use this tool: when creating a new project rather than opening or updating an existing one. It does not explicitly exclude alternatives, but the 'new' wording provides clear contextual guidance without requiring inference.

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