ue_foliage_spawn_volume

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

With no annotations, the description must disclose behavioral traits. It clearly states the result (places a volume with connected spawner), but does not mention side effects, required permissions, inherited transforms, behavior when spawner_path is invalid, or any details about what happens after placement. This is a thin disclosure for a placement command.

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 concise with a one-line purpose followed by a compact list of parameters. No redundant information, front-loaded, and every sentence contributes meaning. This is an efficient and well-structured description.

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 4 parameters, no annotations, and no output schema, the description covers the essential purpose and parameter semantics but lacks usage context and potential caveats. It is sufficient for a simple placement tool, but misses guidance on prerequisites and failure modes, leaving it incomplete for an agent to use confidently.

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. It provides units (cm) and a default for size, and explains the semantic meaning of each parameter (e.g., label is the actor name in the level). However, it does not explain the expected structure of location/size (e.g., Vector vs array), which limits the added value.

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 'Piazza' (Places) and a concrete resource (ProceduralFoliageVolume), and clarifies that the spawner is already connected. This distinguishes it from siblings like ue_create_foliage_spawner, which creates a spawner asset, though it doesn't explicitly name the alternative.

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 'con lo spawner già collegato' implies that a spawner must exist beforehand, but there is no explicit guidance on when to use this tool versus alternatives such as ue_create_foliage_spawner or ue_pcg_spawn_volume. No exclusions or alternative tool references are provided.

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