offset_keyframes

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

With no annotations, the description must convey behavior. It only says 'offset all keyframes in time' without detailing side effects (e.g., whether keyframes are shifted relative to a reference point), in-place modification, or error conditions. This leaves significant ambiguity about the operation's effects.

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, clear sentence with no redundant words. It is appropriately concise for a simple operation, though it could include a bit more detail without becoming verbose.

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 omits critical context: how to specify which keyframes to offset (via layer/property), whether the offset is added or subtracted, and what the tool returns (no output schema is present). The schema is sparse, so the description does not compensate, leaving the tool incompletely specified.

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 schema describes only 'offset' with a unit (seconds). The tool description adds no further explanation for parameters like compId, property, layerName, or layerIndex. It does not clarify how these parameters identify the target layer/property, leaving the caller to infer from names alone.

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 'Offset all keyframes in time' clearly states the action (offset) and the object (keyframes), and specifies the dimension (time). This distinguishes it from sibling operations like scale_keyframe_timing (which scales times) or reverse_keyframes (which reverses order).

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 the use case (shifting keyframes by a fixed time offset) but does not explicitly state when to prefer this over alternatives. No mention of prerequisites (e.g., layer must have keyframes) or conditions that make this tool suitable.

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