Execute Python in TouchDesigner

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

Annotations indicate destructiveHint=true and openWorldHint=true. The description adds the key behavioral constraint that 'Code runs in TD only, never on the local machine,' which goes beyond the annotations and clarifies the execution scope. It does not contradict 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 extremely concise: two sentences that front-load the core purpose and then add usage guidance. Every sentence adds value with 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 the tool's nature as an arbitrary code execution escape hatch, the description covers purpose, usage boundaries, and scope limitation. It does not detail error handling or security implications, but the annotations (destructive, open world) and the 'escape hatch' label imply risks sufficiently. Almost complete.

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 description coverage is 100%, so baseline is 3. The tool description does not add any parameter-specific meaning beyond the schema's existing descriptions. The parameters are adequately described in the schema itself.

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 runs an arbitrary Python script inside TouchDesigner. It uses a specific verb ('run') and resource ('arbitrary Python script inside TouchDesigner process'), and differentiates from structured tools by calling itself an 'escape hatch' and listing the preferred alternatives.

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 explicitly advises to prefer structured tools and to only use this when no structured tool can express the operation. It lists several sibling tools as alternatives, providing clear when-to-use and when-not-to-use guidance.

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