map_object_create

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

With all annotations false, the description carries the full burden. It reveals that the object is created in a live scene and not saved, but fails to disclose other traits like 'allowlisted' requirements, side effects, or whether the operation is immediately visible.

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?

A single sentence achieves high conciseness with zero wasted words, though it could be expanded with key details without becoming verbose.

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 MapObjectMutation schema (many parameters, no descriptions) and the presence of an output schema (not shown), the description is severely incomplete. It fails to explain required fields, value constraints, or the return format.

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%, so the description must compensate. However, it provides no information about parameters such as name, class_name, scale, position, rotation, or fields, leaving the agent to infer from the schema alone.

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), resource (allowlisted live scene object), and a key qualifier (without saving the level). This distinguishes it from related tools like map_object_update and map_save.

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 phrase 'without saving the level' implies a non-persistent use case, but there is no explicit guidance on when to use this tool versus alternatives like map_object_update or map_save.

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