Place a GDevelop object instance

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

Annotations indicate readOnlyHint=false, implying a write operation, but the description adds no further behavioral context. It does not disclose potential side effects, permissions, or behavior regarding existing instances, which is particularly important for a mutation tool.

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 sentence with no filler words, front-loading the core action and resource. Every word adds meaning, making it appropriately concise.

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?

The tool has 10 parameters and no output schema, yet the description is minimal and provides no information about return values, prerequisites, or side effects. Given the complexity, this is insufficient for an agent to fully understand the tool's behavior.

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 is expected to compensate for parameter meaning, but it only mentions 'optional instance variables,' leaving the other nine parameters purely self-explanatory from their names. It fails to clarify relationships, constraints (e.g., exclusiveMinimum for width/height), or the structure of nested variables.

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 specifies the action ('Place') and resource ('initial instance of a scene object'), and mentions optional instance variables, which differentiates it from sibling tools like add_scene_object. However, it could be more explicit about the distinction between placing an instance and adding an object definition.

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 is provided on when to use this tool versus alternatives, and no prerequisites are mentioned (e.g., whether the object must already exist in the scene). The description simply states what it does without contextual usage advice.

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