ue_spawn_many

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

No annotations provided, so description carries full burden. It discloses batch spawning, single undo transaction, and explains input structure with example. Does not contradict any annotations. Minor lack of detail on error handling.

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?

Very concise: one line purpose, one line usage guidance, then Args section. Front-loaded key info. No redundant text.

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?

Covers all necessary aspects for a batch spawn tool: single undo transaction, input structure, and when to use. Lacks explicit success/return value description, but typical for such tools.

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 has no descriptions (0% coverage). Description explains each field in the actors array (class_ref, location, rotation, scale, label) with types and example. Adds crucial meaning beyond the raw 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 the verb 'spawn' and resource 'actors' in batch, using Italian. It explicitly distinguishes from the sibling 'ue_spawn_actor' by highlighting batch operation and single undo transaction.

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?

Provides explicit guidance: use this tool over 'ue_spawn_actor' when spawning many actors (decine di elementi) to avoid multiple HTTP round-trips. Clearly defines when to use.

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