set_anim_frame_rate

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

Annotations only give the safety profile (not read-only, destructive, idempotent), while the description supplies the behavior an agent actually needs: one undo step, automatic package save, partial-failure semantics (success=false, saved=false, save_error), atomic no-change on error, and the no-op note path.

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?

Front-loaded with the core action and the constraint on valid rates. It is dense and slightly run-on across several conditional clauses, but every clause carries actionable constraint or return information rather than filler.

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?

With no output schema, the description fully carries the return contract ({sequence_path, fps, numerator, denominator, changed, saved, save_error, note?}) plus error and save-failure paths. An agent has everything needed to call it and interpret the result.

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 coverage is 100% and both params are documented there, so the baseline is 3. The description adds meaning beyond the schema by stating the rate is rounded to whole fps and that fps/numerator/denominator are read back from the data model, implying the applied rate may differ from the requested value.

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?

Names a precise verb and resource ('Set the frame rate of the data model of a UAnimSequence') and even cites the underlying API (IAnimationDataController::SetFrameRate). It is clearly distinguishable from the level-sequence sibling set_sequence_frame_rate and from the read-side get_anim_sequence_info.

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?

Explicit preconditions for a valid call: the new rate must be a multiple or factor of the current one and the frame count must stay whole, otherwise it is an error and nothing changes. It also states the no-op case (rate already set → success with changed=false) and names get_anim_sequence_info as the way to read the current rate.

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