Pulse a TouchDesigner parameter

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

With no annotations indicating safety, the description adds a basic behavioral clue by identifying the action as 'pulse' and giving typical targets. It does not disclose return behavior, side effects, or prerequisites like needing an active connection.

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, front-loaded sentence with no redundancy. Every word adds value, and examples improve comprehension without added length.

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 tool is simple and the description covers the core action, but no output schema exists and return/error behavior is omitted. The missing schema description for 'parameter' is only partially mitigated by examples, leaving the overall context minimally adequate.

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 schema documents 'path' but leaves 'parameter' unexplained. The description partially compensates by offering example parameter names, but it does not explicitly state that 'parameter' should be the parameter name string or define expected formatting.

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 a specific action verb 'Pulse' and the resource 'momentary parameter' with concrete examples (Reset, Clear, Open). This clearly distinguishes it from sibling tools like td_set_parameters, which persist values.

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 phrase 'momentary parameter' implies the appropriate use case, and examples clarify the intent. However, it does not explicitly state when not to use it or point to an alternative like td_set_parameters for sustained values.

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