particle_add_system

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

No annotations provided, so the description must carry the burden. It indicates the tool adds a particle system (mutation) but does not disclose side effects like scene file modification, required permissions, or return format details beyond 'success message or error'. Adequate but not comprehensive.

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 structured with clear sections (Args, Returns) and is concise—no redundant sentences. Every line adds value, and the format is easy to scan for agents.

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 the complexity (7 parameters, sibling tools, no annotations), the description covers parameters but omits prerequisites (e.g., scene must be open), error conditions, or whether the system is added immediately. The output schema likely fills some gaps, but the description could be more complete.

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?

Input schema has 0% description coverage, leaving the description to explain parameters. It provides a one-line explanation for each of the 7 parameters, including defaults and types, which adds significant meaning beyond schema titles. Slightly lacks detail on particle_type options but overall effective.

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 'Add a particle system to a scene' with a specific verb and resource. It includes parameters that define the action, effectively distinguishing from siblings like particle_set_properties or particle_start_emitting by focusing on creation.

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 explicit guidance on when to use this tool versus alternatives. The description does not mention prerequisites, when not to use, or other tools that might be more appropriate (e.g., particle_set_properties for modification). The usage is implied but not clearly directed.

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