One source five ways

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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds valuable context beyond this: 'offline', 'deterministic', and the specific brief types (colorway, motion, texture, spatial reframe, performance cue). It aligns with annotations and enriches the behavioral profile.

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 two sentences long, front-loaded with the core function, and the second sentence delivers important usage context (offline/read-only, planning purpose). Every word serves a purpose with no redundancy.

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 presence of an output schema, the description correctly avoids detailing return values. It covers the tool's purpose, usage timing, non-mutating nature, deterministic behavior, and output categories, making it complete for a planning tool.

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?

The input schema provides 100% coverage for all five parameters, so the schema itself is fully descriptive. The description only echoes the source input concept ('one source node, asset, or package entry') without adding parameter-specific details, meriting the baseline score.

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 tool's function with a specific verb ('turn') and resource ('one source node, asset, or package entry'), and specifies the exact output ('five deterministic remix briefs' in named categories). It distinguishes itself from sibling creation tools by emphasizing its planning/remix nature.

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?

The description provides clear context: it is an 'offline/read-only planning tool for agents before mutating TouchDesigner networks,' implying use as a precursor to mutation. It does not explicitly name alternative tools or exclusion criteria, but the 'before mutating' guidance effectively communicates when to use it.

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