Delete a TouchDesigner operator

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

Annotations already indicate destructive behavior (destructiveHint=true). The description adds valuable context beyond annotations by stating 'Root and project components are protected by the bridge,' which informs the agent of safety constraints. It also clarifies that only one operator is deleted, setting expectations for the operation's scope.

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 short sentences—with no filler. Each sentence adds functional value: the first states the primary action and scope, the second communicates a key safety constraint. Ideal length for a simple deletion tool.

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 simple one-parameter tool with strong annotations, the description is largely complete. It covers the core behavior and protected cases. However, it does not mention error handling or return behavior, which could be relevant for agents, but given the tool's simplicity and the presence of annotations, this is a minor gap.

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 already provides 100% coverage for the 'path' parameter with a clear description and example. The tool description does not add further parameter-level detail beyond what the schema provides, matching the baseline for high schema coverage.

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 purpose with a specific verb and resource: 'Delete exactly one operator.' It also distinguishes itself from sibling tools like create/set by focusing solely on deletion, and the note about protected components adds specificity.

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 implies usage for deleting a single operator but does not explicitly compare to alternative tools or state when not to use it. The 'exactly one' qualifier and protected-path note give some context, but there is no explicit 'use this instead of X' guidance.

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