Disconnect a TouchDesigner connector

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

Annotations already convey readOnlyHint false and idempotentHint true, but the description adds no additional behavioral context such as side effects, error cases, or prerequisites for disconnection. For a mutation tool, the description fails to disclose anything beyond the bare action.

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 a single sentence, directly to the point with no filler. It earns every word and is optimally concise.

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 mutation tool with no output schema and incomplete parameter descriptions, the description omits essential details about the connector parameter, default behavior, and edge cases. The tool is under-specified for an agent to reliably use it without further clarification.

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 only 33% (only path is described). The description fails to explain the 'connector' integer parameter or the 'direction' enum, leaving the agent without critical information to invoke the tool correctly. No compensation for the schema gap is provided.

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 uses the specific verb 'disconnect' and identifies the resource as 'one input or output connector' on an operator, clearly distinguishing it from sibling tools like td_connect. It is concise and unambiguous about what the tool does.

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?

No guidance is provided about when to use this tool versus alternatives like td_connect or td_delete_operator. The description only states the action without usage context, exclusions, or prerequisites, leaving the agent to infer applicability.

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