editor_create_actor

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

No annotations are provided, so the description must carry the full behavioral burden. It discloses that creation happens in a loaded scene and returns live details, but omits permissions, side effects, reversibility, failure modes for invalid sceneId/parentId, and what happens on name collisions.

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 single sentence is front-loaded with the core action and resource, and every clause contributes useful information without 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?

An output schema exists, so return values need not be explained. However, for a 7-parameter mutation tool with nested objects and no annotations, the description is far too sparse regarding parameter semantics, preconditions, and side effects to be complete.

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 only 14%, with just actorType documented in the schema. The description adds no meaningful semantics for name, sceneId, parentId, translation, orientation, or scale, leaving most required parameters undocumented beyond their types.

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 states a specific verb ('Creates') and precise resource ('allowlisted EmptyActor or StaticModel') within a loaded scene, plus the return behavior. It is clearly a creation tool rather than duplication or modification, though it does not explicitly name sibling alternatives.

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 'in a loaded scene' implies a precondition and 'allowlisted' hints at constraints, but there is no explicit guidance on when to use this versus editor_duplicate_actor, editor_add_script, or other creation siblings. Usage is inferable but not well delineated.

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