anim_set_frame_range

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

No annotations exist, so description must fully cover behavior. It only states the action without mentioning side effects, safety, or constraints (e.g., what happens if start > end, whether existing keyframes are cleared, or if FPS change affects playback). Minimal transparency.

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?

Very concise: one-line summary plus arg list. No wasted words. However, a bit more structure (e.g., clarifying defaults and behavior) could be added without much bloat.

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?

Despite having only 3 simple parameters and no output schema, the description lacks important context like return value, error handling, and relation to animation pipeline. Incomplete for a tool that modifies scene state.

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 has no descriptions (0% coverage). The description adds brief meaning: start and end are frame numbers, fps with 0 meaning 'don't change'. This is helpful but still leaves ambiguity (e.g., valid ranges, order validation). Adequate but not comprehensive.

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 verb 'set' and resource 'scene frame range and optionally FPS' clearly describes the tool's function. It is distinct from siblings like set_frame (current frame) and set_animation_range (possibly similar but not differentiated). The name indicates it belongs to animation tools, so purpose is clear.

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 on when to use this tool versus alternatives. For example, it does not explain why one would use this instead of set_animation_range or other animation tools. Lacks when-to-use and when-not-to-use context.

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