Create Engine COMP

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

Annotations only provide readOnlyHint=false, destructiveHint=false, openWorldHint=true. The description adds significant behavioral traits: subprocess creation, crash domain, optional GPU thread, guarded parameters with hasattr, and warning about multi-second first cook. No contradictions with 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 informative but somewhat lengthy with multiple sentences. It is front-loaded with the main purpose, but some technical details (e.g., hasattr guard) could be condensed without losing clarity.

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?

For a tool with 6 parameters and no output schema, the description covers creation behavior, subprocess details, guard mechanisms, and sibling relationship. It does not explain error conditions beyond the hasattr warning, but overall it is fairly complete given the complexity.

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 description provides context about the reload pulse, perform-mode override, and color-map toggle but does not add significant semantic meaning beyond what the schema already describes for each parameter.

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 creates a TouchDesigner Engine COMP that loads an external .tox in a separate subprocess, specifying the resource and action. It distinguishes from siblings by noting it complements make_portable_tox.

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 indicates ideal usage for heavy or unstable subgraphs and provides caveats about spin-up time. It mentions complementing make_portable_tox but does not explicitly state when not to use or provide alternative tools.

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