set_animation_interpolation_mode

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

Annotations are absent, so the description carries the full burden of behavioral disclosure. It clearly implies in-place mutation of animation resource files, but it does not state whether the file is rewritten, whether the operation is reversible, what happens with invalid modes or track indices, or what the tool returns.

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 summary is front-loaded and the Args section is compact and well-organized. 'Interpolation Mode Swapper' is somewhat redundant with the tool name, but it does not waste meaningful space.

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?

All required input semantics are covered, and an output schema exists, so omitting return-value details is less critical. However, with no annotations, the description is incomplete around side effects, error behavior, and mutation guarantees, so it is only minimally complete for correct invocation.

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, and it does. It explains all three parameters: file_path must be an absolute path, mode has named values with numeric aliases, and track_index uses -1 as a sentinel meaning 'all tracks'. This is substantially more informative than the bare input schema.

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 states a specific action ('Bulk-edit keyframe easing modes') and a specific resource ('.tscn/.tres file'), and enumerates the supported interpolation modes. It does not explicitly distinguish itself from sibling animation tools like quantize_animation_keyframes, but the focus on easing/interpolation modes is clear enough to identify the tool's purpose.

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 alternatives, or when not to use it. The phrase 'Bulk-edit' implies a batch use case and file types are stated, but an agent is not told how to choose this over sibling animation-related tools.

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