Pulse TouchDesigner parameter

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false), the description discloses validation-before-invocation, typed error behavior for missing/non-Pulse cases, and the absence of raw Python fallback. This adds meaningful behavioral context about what happens on failure and what the tool intentionally does not do.

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 core action, and each sentence earns its place: the first explains the process, the second covers error semantics and the no-fallback trait. No redundancy or fluff.

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 pulse tool, the description covers validation, invocation, error behavior, and the no-fallback policy. The only minor gap is the vague 'confirm the result' without specifying return format, but since no output schema exists and the tool is simple, this is 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?

Schema coverage is 100% with descriptive parameter entries ('Full path of the operator that owns the Pulse', 'Exact name of the Pulse parameter'). The description does not add extra meaning beyond what the schema provides, so the baseline of 3 is appropriate.

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 a specific action: 'Validate that an existing operator parameter is Pulse style, invoke its structured .pulse() operation, and confirm the result.' It names the resource (operator parameter), the exact operation (.pulse()), and differentiates from siblings like execute_python_script by noting it does not use raw Python fallback.

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 when to use: for Pulse-style parameters needing a structured pulse call. It clarifies limitations ('Does not use raw Python fallback') and error conditions (missing operators/parameters/non-Pulse styles return typed errors). However, it does not explicitly name alternatives or state 'use this instead of X', leaving some room for inference.

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