Set native GDevelop scene events

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

The description states the tool can 'Replace' events, which implies destructive overwriting of existing content. However, the annotation destructiveHint is false, creating a direct contradiction between the described behavior and the tool's declared destructiveness.

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 filler or redundant information. It is concise, though it sacrifices detail that could have been included without much added length.

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 complexity of the nested events schema and the lack of an output schema, the description is incomplete. It omits usage context, side effects of replacing events, parameter details, and any return value information, leaving the agent with insufficient guidance 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?

Schema description coverage is 0%, and the description does not name or explain parameters like projectId, sceneName, events, or mode. It only vaguely maps 'Replace or append' to the mode parameter and lists event types without explaining the structured events 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 uses specific verbs 'Replace or append' and identifies the resource as 'native GDevelop comments, groups, and standard events.' This clearly distinguishes it from sibling tools like set_scene_javascript, which handles JavaScript instead of native events.

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 modifying scene events but provides no explicit guidance on when to choose this tool over alternatives. The word 'native' hints at a distinction from JavaScript-based tools, but no direct when-to-use or exclusion guidance is given.

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