Generate art from a moodboard note

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

Discloses side effects (node creation, no file writes), the best-effort nature of color hints, and that it returns the same network as create_generative_art, adding value beyond 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?

Two sentences pack all essential information: action, side effects, usage guidance, and prerequisites. No wasted words.

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 all aspects: input, behavior, output, prerequisites, and alternatives. No missing information despite lacking an 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?

Schema coverage is 100% with parameter descriptions, and the description does not add significant new semantic detail beyond what is already in the schema (e.g., note resolution, technique override). Baseline 3 is appropriate.

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 it reads a moodboard note and creates a generative system in TouchDesigner, distinguishing itself from the sibling tool create_generative_art by specifying the use case for moodboard-based seeding.

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 this tool ('to seed a system from a vault moodboard') and when to use the alternative ('call create_generative_art directly'), plus mentions 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.