TD Build Pattern (live)

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

Discloses key behaviors: creates operators in workflow order, wires as straight chain, lays out network, limitation on multi-input, hard-errors if operator name missing createType, requires bridge. No annotations provided, so description carries full burden and does so thoroughly.

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?

Single paragraph but well-structured with key points in caps for emphasis. Each sentence adds meaningful information without redundancy. Slightly verbose but justified by the complexity.

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 and absence of output schema, the description covers workflow, limitation, default parent, and error handling. Could mention behavior on existing operators in sandbox, but overall complete enough for agent to use correctly.

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%, so baseline is 3. The description adds value by explaining what 'pattern' means (name in data/patterns.json with examples) and the default for 'parent', going beyond schema descriptions.

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 the verb 'COMPILE' and the resource 'linear workflow pattern from data/patterns.json', specifying that it builds into a running TouchDesigner instance. It explicitly differentiates from sibling tool td_build_template for branched networks.

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?

Explicitly states when to use (linear single-input chains) and when not to (multi-input nodes), with a direct alternative: 'use td_build_template for branched networks'. Also mentions default parent and error behavior, providing clear usage context.

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