generate_particle_burst

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

With no annotations present, the description must carry the behavioral disclosure burden. It does reveal that the output is deterministic and GIF-formatted, but it does not clarify side effects such as file creation, overwriting behavior, output location, or whether the burst is generated against the current canvas/sprite context.

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 a single focused sentence with no redundant phrasing. It front-loads the most important facts, though it is concise at the cost of omitting useful behavioral and parameter context.

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?

This tool has 8 parameters, 7 required, no annotations, no output schema, and 0% schema-description coverage. A one-sentence purpose statement is not enough to correctly invoke a particle-burst generator; the agent is left guessing about output format specifics, parameter effects, and side effects.

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 needs to compensate by explaining how parameters like seed, color, frames, and particle_count interact. It adds no parameter-level meaning beyond what the parameter names already imply, leaving key semantics such as deterministic seeding unexplained.

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 names a specific verb and resource: 'generate a deterministic animated particle burst GIF'. It also gives concrete usage categories (impact, healing, magic, dust) and the 'deterministic' qualifier distinguishes it from generic animation or GIF-generation siblings.

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 'for impact, healing, magic, or dust' gives an implied use case, so an agent knows this is for particle-burst-style visual effects. However, it does not explicitly state when to prefer this over alternatives such as generate_motion_pack or export_animation_gif, nor does it give any when-not conditions.

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