Create audio-reactive visual

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

Adds value beyond annotations by explaining that frequency_bands is clamped by TouchDesigner and detailing visual_style renderings. Annotations indicate openWorldHint=true but description doesn't fully clarify side effects (e.g., whether existing nodes are modified).

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?

Two sentences, front-loaded with main action, no redundant information. Every sentence adds value.

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?

Covers main functionality but lacks return value (no output schema), full parameter details, and usage context. Some gaps remain given 8 parameters and no output schema.

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?

Description clarifies visual_style rendering modes and frequency_bands behavior, which are not fully described in schema. With 50% schema coverage, description compensates well but lacks details for audio_source and parent_path.

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?

Description uses specific verb 'build' and clearly identifies the resource: an audio analysis chain and spectrum visual. It differentiates visual_style options with rendering details, distinguishing from siblings like create_3d_audio_reactive and create_spectrum.

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 when-to-use or when-not-to-use guidance. Sibling tools like create_3d_audio_reactive exist but aren't mentioned. Context is implied but not clarified.

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