batch_spawn

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

No annotations are provided, so the description must disclose behaviors. It states the action but does not explain failure handling, atomicity, return values, or permissions. Referencing actor_spawn for format is helpful but insufficient for a batch operation.

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?

Two sentences, front-loaded with the main purpose, and the second sentence directs to a sibling for format. No wasted words.

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 batch operation with nested object parameters and no output schema or annotations, the description is too sparse. It does not explain what the call returns, whether it is atomic, or how errors are handled. The reader must infer from actor_spawn, but even that may not cover batch-specific behavior.

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?

The description points to actor_spawn for the format of each spawn definition, which is a strong reference. The schema lists the fields, but without this reference, parameter meanings would be unclear. This compensates for lack of individual field descriptions.

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 spawns multiple actors in one call, using a specific verb and resource. It distinguishes from the sibling actor_spawn by the batch nature, though it does not explicitly contrast them.

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 implies use for batch spawning when multiple actors are needed, but does not explicitly state when to prefer this over repeated actor_spawn calls. There is no mention of exclusions or alternatives.

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