anim-set_interpolation

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

With no annotations, the description carries the burden of behavioral disclosure. It does reveal that the operation modifies every keyframe on an object's f-curves, which is useful, but it does not mention that existing interpolation settings will be overwritten, that object defaults to active, or any side 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, front-loaded sentence with no filler. It earns its place by naming the operation, target, and scope, making it highly scannable for an agent.

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?

For a simple two-parameter setter, the description covers the core operation, but it lacks usage guidance, parameter depth, and behavioral caveats. There is no output schema, so return values are not required, but the absence of annotation support and alternative-tool context leaves it only minimally complete.

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 should compensate. It adds a bit of context about f-curves and keyframes, but it does not explain the interpolation enum values or elaborate on the object parameter beyond what the schema title already says. The description largely restates the schema's property titles.

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 uses a specific verb and resource: 'Set interpolation for all keyframes on an object's f-curves.' It clearly distinguishes this tool from animation siblings like anim-insert_keyframe or anim-set_frame by focusing on interpolating existing keyframes across f-curves.

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 phrase 'all keyframes' implies this is for batch-changing interpolation on existing f-curves, but there is no explicit guidance on when to use it versus anim-keyframes, anim-set_timeline, or other animation tools. Context is implied rather than stated, and no alternatives or exclusions are mentioned.

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