Create POP particle system

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

The description goes beyond annotations by disclosing the noiseTOP fallback when force_texture_path is omitted, the three output modes, delegation to build_pop_chain, and the experimental status with an unverified marker. Annotations (readOnlyHint=false, openWorldHint=true, destructiveHint=false) are consistent, and the description adds valuable operational context 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?

Despite its length, the description earns its space: it front-loads the core action, then covers fallback behavior, output modes, scope delegation, alternatives, and a warning. Every sentence contributes new information without redundancy or fluff.

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 complex tool with 8 parameters and no output schema, the description fully covers the creation scope, exact operator chain, default behaviors, output options, delegated helper, and experimental status. The only omission is an explicit return value, but given the tool creates a network, this is adequately implied by the context.

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 coverage is 100% and each parameter already has descriptive text. The description adds extra meaning for force_texture_path (default noiseTOP creation) and clarifies output mode semantics, but most parameter details remain in the schema. This is slightly above the baseline 3 due to the added fallback behavior.

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 uses a specific verb and resource: 'Build a complete POP particle simulation (particle_pop → feedback_pop → lookup_texture_pop → field_pop → null_pop) inside a new baseCOMP, wire a render rig... and expose live controls.' It clearly distinguishes itself from siblings by naming the exact operator chain and output modes, leaving no ambiguity about what the tool does.

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?

Explicit guidance is given with alternatives: 'This is the only particle tool built on TouchDesigner's native POP operators... pick a sibling instead for non-POP paths: create_gpu_particle_field..., create_particle_flock..., image_to_particles..., create_particle_system...' It also clarifies the tool's limited scope by delegating chain creation to build_pop_chain, so the agent knows exactly when to use this tool.

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