anim_play

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

Annotations already declare readOnlyHint=false and destructiveHint=true, so the safety profile is known. The description adds no behavioral context beyond restating the three actions; it does not disclose side effects, what happens on stop, or any state changes beyond playback control.

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 definition is short and front-loaded, with the operation summary before the action mapping. The bilingual repetition and the redundant action= sentence add slight noise, but overall it remains appropriately compact.

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?

The core actions are covered and the optional frame parameters are documented in the schema. The description is incomplete in that it never specifies viewport versus preview playback, the effect of fromFrame/toFrame during pause/stop, or expected return behavior.

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 100%, so the baseline is 3. The description's action= mapping only restates the enum names and does not add meaningful semantics beyond what the schema already provides for action, fromFrame, or toFrame.

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 clearly names a specific resource ('the animation') with explicit verbs: play, pause, stop. However, it does not distinguish itself from the closely named sibling anim_play_preview or clarify whether it controls viewport playback, so sibling differentiation is missing.

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?

There is no guidance on when to use this tool versus alternatives such as anim_play_preview or anim_goto_frame. The action enum implies playback control, but no conditions, exclusions, or alternative routing are provided.

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