playback.set

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

Annotations already declare readOnly, idempotent, and non-destructive behavior, so the description's 'Risk: read' adds little. It does add non-obvious operational context beyond annotations: maturity L3, per-request checks, and the VIEW_3D foreground requirement. It does not contradict the annotations.

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 text is short and front-loaded, but it is under-specified rather than concise. The first sentence merely restates the command name, and the rest is metadata that could be carried by annotations; there is no core functional sentence.

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?

While the output schema and annotations cover return values and safety, the description omits the tool's core purpose and parameter semantics. Given over 100 siblings and a direct sibling `blender_playback_set_frame`, this is not enough context for an agent to select and invoke the tool correctly.

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 only 60% and the required `playing` parameter has no schema description. The tool description does not explain the meaning of true/false or the effect of the parameter, so the agent is left to guess from the parameter name.

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 opens by restating the command name (`playback.set`) and then gives risk/maturity metadata, but never says what the tool does. An agent must infer from the title and the `playing` boolean that it controls animation playback. It also does not distinguish this from the closely named sibling `blender_playback_set_frame`.

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?

It provides explicit prerequisites: per-request argument checks, session policy, and a foreground VIEW_3D area. This is useful context but only implies the intended use case and mentions no alternative tools or when to choose one over `blender_playback_set_frame`.

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