set_keyframe

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

With no annotations, the description carries the full burden of disclosing behavior. It states the action but does not reveal whether existing keyframes are overwritten, what happens if the parameter is not keyframable, or whether the operation returns anything. The phrase 'set' implies mutation, but important side effects and prerequisites are omitted.

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 unnecessary words. It is appropriately concise for a straightforward tool, though it is arguably under-specified; however, conciseness is not the issue here. It scores slightly below 5 because it could have included a brief clause about parameters without bloating the text.

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 4 required parameters, no annotations, no output schema, and zero schema descriptions, this description is severely incomplete. It does not explain the meaning of the required parameters, expected value types, or any return behavior. An agent would struggle to invoke this tool correctly without external documentation.

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 0%, so the description must compensate by explaining parameter meanings. It does not. The description only mentions 'parameter' and 'frame' generically, without clarifying how node_path, parm_name, frame, and value should be provided or what formats/ranges are expected. No additional semantics beyond the schema titles are given.

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 specifies the action: 'Set a keyframe on a parameter at a specific frame.' It uses a specific verb ('set') and resource ('keyframe on a parameter'), and explicitly mentions 'a specific frame,' which distinguishes it from the sibling set_keyframes (plural). The singular 'a keyframe' helps differentiate from batch 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?

No guidance is provided on when to use this tool versus alternatives like set_keyframes, delete_keyframe, or set_parameter. The description only implies the basic scenario of setting a single keyframe but does not mention exclusions or conditions (e.g., parameter must be animatable, or when to prefer set_keyframes).

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