Animate parameter

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

The description discloses key behaviors: creates LFO CHOP, binds targets, switches to expression mode. It does not mention side effects like performance or re-invocation behavior, but annotations provide safety hints (non-destructive, open world).

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?

Two sentences with no wasted words. Front-loaded with core purpose, immediately informative.

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 main behavior and parameter usage adequately. With 7 parameters all described in schema, the description fills the gap for behavioral context. No output schema, but return value is implied.

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%, and the description adds context beyond schema, e.g., target format and behavior, waveform range sweep. This adds meaningful value despite 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 drives node parameters over time using an LFO, distinguishing it from manual keyframing. It specifies verb, resource, and mechanism, effectively differentiating from siblings like create_keyframe_animation.

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 use for parameter animation without manual keyframing, creating a clear contrast. However, it lacks explicit when-not-to-use or alternative guidance, though the contrast is strong.

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