Create POP particle system

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

The description adds valuable behavioral context beyond the annotations: it explains that a noiseTOP is created when force_texture_path is omitted, notes that POPs are Experimental and carry an unverified marker, and discloses the delegation pattern. Annotations already indicate readOnlyHint=false, destructiveHint=false, and openWorldHint=true, and the description aligns with these without contradiction.

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 fairly long but each sentence adds meaningful detail about the tool's behavior, output modes, and important caveats. It is well-structured with key points, though a slight reduction in verbosity could improve conciseness without losing clarity.

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 tool's complexity (8 parameters, no output schema, no nested objects), the description covers most essential aspects: the node chain built, output modes, parameter mappings, and the default behavior for missing arguments. However, it lacks information about the return value (e.g., what path the tool returns) and potential error conditions, which would improve completeness.

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 significantly enhances the schema by explaining how each parameter maps to specific attributes in the generated nodes (e.g., emission_rate mapped to particle_pop birthrate and exposed as EmissionRate knob). It also clarifies the special behavior of force_texture_path, which triggers creation of a default noiseTOP if omitted. This goes well beyond the parameter descriptions in the 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 it builds a complete POP particle simulation with a specific node chain, render rig, and live controls. It distinguishes itself from siblings like build_pop_chain by noting that the POP chain creation is delegated, while this tool adds the render rig and control exposure.

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 provides good context on when to use this tool, mentioning that it delegates POP chain creation to build_pop_chain and noting that POPs are Experimental with a live-validation requirement. However, it does not explicitly exclude alternative particle tools (e.g., create_particle_system, create_gpu_particle_field), so there is room for more precise guidance.

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