spawn_volumetric_cloud

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

Annotations only cover the generic readOnly/destructive/idempotent profile, while the description adds genuinely non-obvious behavior: it runs as one undoable transaction, it does not check for an existing cloud (so duplicates are possible), and it does not persist anything. These are exactly the facts an agent needs before invoking.

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?

Front-loaded with the action and its constraints, then the tuning pointer. Slightly wasteful because return values are stated twice, once inline and again in the structured 'Returns:' block, but overall tight and readable.

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?

For a one-parameter spawner with no output schema, the description covers everything: what is created, where, the transactional and persistence semantics, the follow-up tool, and the full return shape. Nothing needed to call it correctly is missing.

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 100% and the single location parameter is fully documented there, so the schema does the heavy lifting. The description adds only the minor clarification that no rotation is supplied; otherwise it does not extend parameter meaning 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?

Specific verb (Spawn) plus specific resource (VolumetricCloud actor) plus scope (editor world, at location, no rotation). An agent can distinguish this from sibling spawners like spawn_sky_light or spawn_post_process_volume without opening any schema.

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?

States a clear usage context ('without checking for an existing one', 'nothing is saved') and routes the agent to set_volumetric_cloud_properties for the follow-up tuning step. No explicit when-not or named alternative among the other spawn_* tools, so it stops short of a 5.

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