Set a GDevelop scene variable

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

Annotations already mark it as not read-only. The description adds only that the variable is 'editable' and accepts certain value types, which is largely redundant with schema. It does not disclose overwrite behavior, scene existence requirements, or 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?

Single sentence, concise, front-loaded with action. No filler.

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 setter, the description covers the main purpose and value type limitations. It leaves out overwrite/merge semantics but overall is sufficient given the straightforward nature of the tool.

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 explains the 'value' parameter can be primitive, structure, or array, aiding interpretation of the recursive schema. However, projectId, sceneName, and name are not elaborated beyond their self-explanatory names.

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 uses specific verb 'Create or update' with resource 'editable scene variable' and enumerates value types, clearly distinguishing from sibling set_global_variable. It is specific and unambiguous.

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 use for scene variables but provides no explicit guidance on when to choose this over set_global_variable or other sibling tools. No alternatives are named.

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