animation_setInterpolation

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

No annotations are provided, so the description must fully disclose behavioral traits. It mentions the action and modes but does not explain side effects, error behavior (e.g., if the keyframe does not exist), whether changes are reversible, or any permission requirements. This is a significant gap for a mutation tool.

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 that includes the resource, action, and valid modes. It is concise with no redundant information.

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 tool is simple with four well-documented parameters, but the lack of annotations and output schema means the description should offer more context. It does not specify what happens if the keyframe is missing, whether the mode overwrites existing easing, or if the operation is destructive. Given the straightforward nature, it is minimally adequate but not comprehensive.

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 100% — all four parameters (layerId, channel, frame, mode) are described. The description adds no extra parameter semantics beyond the schema, so the baseline of 3 applies.

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 sets the interpolation/easing mode on an existing keyframe, listing the specific modes. This distinguishes it from sibling tools like animation_setKeyframe, which sets keyframe values, and animation_getKeyframes, which reads keyframes.

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 usage on existing keyframes and provides the valid modes, but does not explicitly contrast with alternatives (e.g., animation_setKeyframe) or describe when to choose this tool over others. No exclusions or alternative suggestions are given.

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