set_keyframes

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

With no annotations provided, the description carries full responsibility for behavioral disclosure. It only states the action, with no mention of side effects such as whether existing keyframes are overwritten, whether a cook is triggered, or error conditions. This is a significant gap.

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 extremely concise: two short sentences that immediately convey the main action and the keyframe format. No redundant information is present.

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 lack of annotations and output schema, the description should provide more behavioral and contextual detail. It omits return values, handling of existing keyframes, and differences from sibling tools, making it insufficient for an agent to fully understand the tool's implications.

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 description adds meaning for the 'keyframes' parameter by clarifying its structure ('Each: {frame, value}'), which the schema leaves vague (additionalProperties as number). However, it does not explain 'node_path' or 'parm_name,' despite 0% schema description coverage, so it only partially compensates.

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's action and resource: 'Set multiple keyframes.' It also specifies the structure of each keyframe ('Each: {frame, value}'), which distinguishes it from the singular sibling tool 'set_keyframe' and other keyframe operations.

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?

There is no guidance on when to use this tool versus alternatives like 'set_keyframe' or 'set_parameter.' The description does not mention exclusions, prerequisites, or scenarios where this tool is preferred, leaving usage to inference from the name.

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