workflowmoves_compose_epk_cover

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

Beyond the annotations, the description discloses the asynchronous retained-job model, the required polling behavior, the base write effect, and the possibility of conditional inference/download effects. It does not explain output content, but an output schema exists, and the behavioral context supplied is meaningful.

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 description is only three sentences, front-loads the core action, and wastes little space. The phrase "Base effect flags: write" is dense but useful, though the overall wording is slightly jargon-heavy.

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 description covers the key lifecycle behavior and effect flags, which are important for this background-job tool. However, for a nested schema with undocumented source/output/cover arguments, it leaves the caller without enough semantic guidance about how to populate the required fields.

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 50%, with the four nested required arguments (source, output, cover_url, cover_alt) having no descriptions. The description loosely implies a source HTML input and artwork/cover handling, but it does not explain what each parameter should contain or how output paths and cover fields are interpreted.

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 gives a specific verb and resource: "Compose a local artwork-first player from fresh source HTML." It is clear enough to distinguish this from generic workflow tools, but it does not explicitly differentiate it from the sibling workflowmoves_compose_epk_playback, and "artwork-first player" remains somewhat opaque.

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 post-call guidance by explaining that the tool returns a retained background job and that the caller should poll danceflow_job_status. It also points to danceflow_component for conditional effects, but it does not state when to choose this tool versus the related compose_epk_playback sibling or any prerequisites.

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