Generate art from a moodboard note

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

The description discloses key behavioral traits beyond annotations: side effects are node creation in TD, not file writes; color is only a best-effort hint; and a configured TDMCP_VAULT_PATH is required. It also states the return value, providing clear expectations without contradicting the annotations.

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 three dense sentences with no filler. It front-loads the core READ/CREATE action and then delivers necessary side-effect, alternative-use, and prerequisite details efficiently.

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?

Despite having no output schema, the description explains the return value, side effects, input source, alternative invocation, and prerequisite. This is sufficient for an agent to correctly select and invoke the tool for the intended moodboard-to-system workflow.

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 the baseline is 3. The description adds value by explaining the frontmatter fields (technique/palette/colors/speed) and clarifying that the palette is only a best-effort color hint, which enriches the meaning of the 'note' parameter beyond 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 the verb-resource pair: READ a moodboard note and CREATE a generative system in TouchDesigner. It further differentiates from the sibling create_generative_art by explaining that this tool reads a vault moodboard instead of taking inline parameters.

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?

It explicitly tells the agent when to use this tool: 'Use this to seed a system from a vault moodboard.' It also names the alternative, 'call create_generative_art directly to specify the technique and palette inline,' and identifies the prerequisite TDMCP_VAULT_PATH.

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