add_keyframes

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

With no annotations, the description must disclose behavioral traits, but it only says 'Add many keyframes at once'. It does not explain whether keyframes overwrite existing ones, what happens if the animation doesn't exist, or any authorization or side effects. The mutation aspect is implied but not detailed.

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 very concise: two sentences with no wasted words. It front-loads the core purpose and then gives the data shape. Every sentence adds value.

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 no output schema, no annotations, and parameters that need explanation, the description is incomplete. It lacks details on return values, error handling, prerequisites, and constraints. For a mutation tool, more context on behavior and success/failure indicators is necessary.

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 carries responsibility. It lists the fields of the keyframe object (bone, channel, time, value, interpolation), adding some structure beyond the schema. However, it does not explain field semantics (e.g., bone refers to which bone, time units, or interpolation options), leaving the agent to infer from names.

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 adds many keyframes at once, positioning it as the efficient batch version. It distinguishes from the sibling tool 'add_keyframe' implicitly by highlighting 'many at once' and 'author a full 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 bulk keyframe insertion when creating full animations, but does not explicitly mention when not to use it or contrast with single-keyframe alternatives like 'add_keyframe'. No exclusions or prerequisites are stated.

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