set_keyframe

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

With no annotations provided, the description carries the full burden of behavioral disclosure, but it only says 'set a keyframe.' It does not indicate whether an existing keyframe at the given time is replaced, how interpolation defaults behave, whether the operation mutates the project, or what happens when multiple comps/layers match the selection criteria.

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 short sentence with no filler, making it easy to parse and front-loaded. Its brevity is structurally clean, though it sacrifices substantive context that other dimensions capture.

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 7 parameters, no annotations, no output schema, and a large family of sibling keyframe tools, the description is incomplete. It does not explain how a target layer or composition is identified, what value shapes are expected beyond the schema enum, or what the result of the operation looks like.

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 only 43%, so the description needs to compensate, but it adds almost nothing beyond the word 'property.' It does not explain how compId, compName, layerName, and layerIndex are resolved, which is a major missing selection semantic for a 7-parameter tool.

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 a specific action ('Set a keyframe') and an object ('a property'), so an agent can tell this is a keyframe-insertion tool rather than a query or easing operation. However, it does not explicitly differentiate it from the similarly named sibling set_keyframe_advanced or other keyframe-modification tools.

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 given for when to use this tool vs set_keyframe_advanced, apply_easy_ease, offset_keyframes, or get_keyframes. The description is only a verb phrase and provides no exclusions, prerequisites, or contextual decision support.

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