Animate parameter

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

Annotations provide readOnlyHint=false and destructiveHint=false, indicating mutation but not destruction. The description adds that it creates an LFO CHOP, binds targets, and switches to expression mode. However, it does not disclose potential side effects like overwriting existing expressions or the behavior when container_path is omitted. The description provides moderate additional context beyond annotations.

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 long, front-loaded with the core purpose, and contains no extraneous information. Every word earns its place, making it efficient and easy to parse.

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?

Given the tool has 7 parameters all documented in the schema and no output schema, the description covers the essential behavioral aspects. It explains the mechanism (LFO CHOP, expression mode) and the predictable oscillation behavior. Missing details like error handling or default behavior for container_path are covered in parameter descriptions. Overall, it is fairly complete for a straightforward animation tool.

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 100%, so the input schema already documents all 7 parameters thoroughly. The tool's main description adds no parameter-specific information beyond what the schema provides. Therefore, the description offers no added value for parameter understanding.

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 animates node parameters using an LFO oscillator. It specifies the resource (LFO CHOP) and action (drive parameters, bind targets), but does not explicitly differentiate from sibling tools like 'create_keyframe_animation' or other animation methods.

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 automated oscillation without manual keyframing, but does not explicitly state when to use this tool versus alternatives, nor does it provide context on when not to use it. No usage exclusions or alternative references are given.

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