anim_set_interpolation

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

With no readOnly/destructive annotations, the description carries the full burden of disclosing behavior, but it only lists interpolation values. It does not say whether this mutates keyframe data, requires existing F-curves, affects a single object or scene, or has 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 text is short, but this is under-specification rather than effective conciseness. A single value enumeration does not earn its place because it omits essential purpose and usage 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?

For a tool with three parameters, no output schema, and no behavioral annotations, this description is far too incomplete. An agent cannot determine what object/data_path refer to, what interpolation is applied to, or how this differs from related animation tools.

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 must compensate, but it only documents valid values for the interpolation parameter. The meanings and usage of object_name and data_path are left completely unexplained.

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 is only a value list — 'interpolation: BEZIER, LINEAR, CONSTANT.' — and never states a verb or target resource. It relies entirely on the tool name and annotation title to imply 'set interpolation' on some animation property, making the purpose vague rather than explicit.

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 about when to use this tool versus sibling animation tools such as anim_insert_keyframe, anim_bake, or anim_set_timeline. There are no stated conditions, prerequisites, or exclusions.

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