Create video synth

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

Annotations already indicate non-read-only, non-destructive. The description adds context about creating a new container, output as Null TOP, and returning parameters/preview. It does not address potential side effects like overwriting existing containers, but given the annotation coverage, this is sufficient.

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 appropriately sized, front-loaded with the core action, and every sentence serves a purpose (action, distinction, alternative, return value). The first sentence is long but packs necessary detail without waste.

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 9-parameter generator with no output schema, the description covers creation, output container, live controls, and return value. It lacks explicit mention of preconditions like parent_path existence, but is otherwise complete enough for selection and basic use.

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 covers all 9 parameters with descriptions (100% coverage). The description mentions live Speed/FreqX/FreqY/Scale/Color controls but does not add meaning beyond the schema's own parameter docs, so baseline 3 applies.

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 a specific action ('Instantiate an analog video-synthesizer pattern... into a GLSL TOP') and defines the output ('output as a Null TOP inside a new container'). It distinguishes itself from siblings by naming create_shader_lib and create_video_player as alternatives.

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?

Provides explicit guidance: 'distinct from create_shader_lib's tunnel/raymarch/fractal/metaball looks' and 'Use create_video_player instead when you want to play a real movie file.' This tells the agent when to pick this tool vs others.

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