Generative classics recipe pack

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

Annotations declare destructiveHint=true, and description confirms by stating 'writes a portable bundle JSON'. Adds context about being pure Node, avoiding bridge. No contradiction.

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 with three sentences, front-loads purpose. Efficient, though could be slightly more structured (e.g., bullet points). 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?

Given 3 parameters, no output schema, description adequately covers behavior, output format (technique cards + list of recipes, bundle JSON), and environment requirement. Not missing critical info.

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 100% of parameters, but description adds meaning: explains what list_only controls, default install_path location, and overwrite flag behavior. Exceeds schema alone.

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 clearly states it is a curated technique pack of generative looks, and specifies two modes (list_only vs full export). This distinguishes it from siblings like 'curated_collection_pack' or individual 'create_*' tools.

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?

Describes when to use each mode (list_only vs false) and highlights 'Pure Node — no TouchDesigner bridge required'. However, it does not explicitly state when NOT to use or compare with alternatives like 'curated_collection_pack'.

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