play_animation

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

No annotations are provided, so the description carries the full burden of behavioral disclosure, and it discloses nothing. It does not state whether playback is started in the viewport, whether the call blocks until the animation ends, what state is mutated (e.g., current frame position, playback toggle), or whether it is safe/idempotent. For a tool with zero annotation coverage, this is a total failure of 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?

The entry is short, but this is under-specification rather than conciseness. The single sentence contributes zero information beyond what the tool name already conveys, so it does not earn its place. A minimal viable description would at minimum state the verb and object, e.g., 'Starts playback of the active animation in the viewport.'

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 an output schema and no parameters, the description leaves the tool's entire behavior undefined. An agent has no way to know what side effects occur, what the expected sequence is relative to stop_animation or set_frame, or what the response will contain. Given the large sibling set around animation control, this description is completely inadequate 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?

The tool has zero parameters, which per baseline earns a 4 regardless of description content. There is nothing for the description to document here, so no points are lost on this dimension. However, the description also fails to add any referential context that might clarify what 'animation' means in scope.

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 'Blender Studio Pro MCP: play_animation' — a namespace prefix followed by the tool name itself. This is a pure tautology that restates the identifier without stating a verb, resource, or effect. An agent cannot tell whether this starts viewport playback, steps through frames, or launches an animation render; a sibling named stop_animation implies it is the inverse, but that inference exists in the sibling list, not in this description.

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?

The description offers no guidance on when to invoke this tool versus any of its roughly 250 siblings. There is no mention of prerequisites (e.g., an open scene), no mention of how it relates to stop_animation, set_frame, or render_turntable, and no exclusion criteria. The agent is left without any decision context.

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