Apply a TouchDesigner edit batch

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

The description discloses rollback behavior—if one edit fails, completed edits are undone when rollback is enabled. It also emphasizes the ordered execution of edits, which is significant behavioral context beyond the annotations. The annotations only state destructiveHint=true, so the description adds value by specifying failure semantics.

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, front-loaded with the primary purpose and a key behavioral detail. No filler words; every element adds value.

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?

The description covers the core purpose and rollback behavior but omits details about the operations array structure, the rollbackOnError parameter, and behavior without rollback. For a tool supporting eight methods and multiple operations, this is only minimally complete. However, the schema provides the method enum, and there is no output schema, so some gaps are acceptable.

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?

With 0% schema description coverage, the description should compensate by explaining the parameters, but it does not. It fails to mention that 'operations' is an array of method/params objects or that 'rollbackOnError' controls rollback. The description only hints at the concept of edits, leaving parameter usage undocumented.

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: applying up to 100 ordered graph edits. The phrase 'Apply up to 100 ordered graph edits' distinguishes it from sibling tools that handle individual operations such as td_create_operator or td_set_parameters. The title reinforces the batch 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 indicates the tool is for applying multiple edits in order with optional rollback, which implies its use case for batch operations. However, it does not explicitly mention alternatives or when not to use it, though the context of a batch tool vs individual tools is clear.

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