ue_sequence_add_actor

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

The description explains the critical behavioral difference of the spawnable parameter, clarifying that True makes the sequence manage its own copy while False animates the existing actor. However, with no annotations, it does not disclose side effects, prerequisites (e.g., sequence must exist), or failure modes.

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 single-sentence summary followed by a clear Args list. No redundant information, though the Italian language might limit accessibility for non-Italian users.

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?

The description covers the core operation and parameter semantics but omits prerequisites (e.g., whether the sequence must already exist), return type, and error handling. Given the lack of output schema and annotations, this leaves the agent to infer some operational context.

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?

With 0% schema description coverage, the description compensates by explaining all three parameters in the Args block. It gives meaningful semantic context for spawnable and labels, though sequence_path could be more specific about valid path format.

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 tool adds a level actor to a sequence with the verb 'Aggiunge' (adds). It includes parameter details that reinforce the purpose, though it doesn't explicitly differentiate from sibling sequence tools like ue_sequence_add_track.

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?

No guidance on when to use this tool versus alternatives like ue_spawn_actor or ue_sequence_add_track. The description only explains what the tool does, not context or exclusions.

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