spawn_actor

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

With no annotations provided, the description carries the full burden. It discloses the creation action and mentions 'PropertyCoercion' for properties, but lacks details on error states, required permissions, or side effects like overwriting labels.

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 two sentences: the first covers purpose and optional parameters, the second gives class path examples. No redundant information; every sentence earns its place.

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 5 parameters with full schema descriptions and no output schema, the description is reasonably complete. It could mention the return value (e.g., spawned actor reference), but the core functionality is well covered.

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 coverage is 100%, so all parameters are described. The description adds value by providing class path format examples and explaining that properties are applied via PropertyCoercion, which goes beyond the 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 clearly states 'Create an actor in the current editor world at a location with optional rotation, label, and initial properties.' It specifies the action (create) and resource (actor), and distinguishes from sibling tools like delete_actor or find_actors_by_class by focusing on spawning new actors.

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 implicitly indicates this is for spawning new actors, but does not explicitly state when not to use it or mention alternatives like set_actor_transform for modifying existing actors. Usage context is partially clear.

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