workflowmoves_compose_epk_playback

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

Goes meaningfully beyond the annotations by disclosing that the call returns a retained background job rather than finished output, that the base effect set is 'write', and that inference/download effects are conditional and must be checked via danceflow_component. That is real async and permission behavior an agent cannot read off readOnlyHint=false/destructiveHint=false. It stops short of saying whether an existing file at the output path is overwritten or how the retained job is cleaned up.

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?

Three tight sentences, zero filler, with the core action stated first and the job-polling requirement immediately after. Every clause carries operational information.

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?

An output schema exists and annotations cover the safety profile, so those need not be restated. What remains missing for a write-producing compose tool is the meaning of source/bindings/output, overwrite behavior, and where the generated HTML lands — all left for the agent to guess.

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 only 50%, and the description adds no meaning for the three required nested fields (source, bindings, output) — no format, path semantics, or expected content. Only the permissions object carries a schema description, and the description's 'base effect flags: write' merely echoes it. The heavy lifting for the most-used parameters is missing on both sides.

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?

States a specific verb and resource: composing reviewed explicit player mappings into new local HTML. It is distinguishable from the sibling workflowmoves_compose_epk_cover by targeting playback rather than cover output. The jargon ('player mappings', 'EPK playback') is not unpacked, but the operation is identifiable.

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?

Implies a prerequisite ('reviewed' mappings) and gives concrete follow-up routing by naming danceflow_job_status for polling and danceflow_component for conditional effect inspection. It never states when to choose this over workflowmoves_compose_epk_cover or what disqualifies a use, so selection between the two compose tools is left to inference.

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