likenessforge_download_model

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

Annotations already declare readOnlyHint=false and openWorldHint=true, and the description adds meaningful context beyond them: the call returns a retained background job rather than completing inline, and the base effects are write/download/network with conditional inference/download effects depending on the component. It stops short of saying what happens on a failed or partial download, but the async and effect disclosure is genuinely useful.

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 short sentences with no filler, and the action is front-loaded ahead of the follow-up polling instruction and the effect disclosure. Nothing is redundant with the annotations or schema.

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, so return values need no prose, and the description still usefully flags the async job model. For a network-touching mutation with nested arguments, the remaining gap is failure/permission behavior and the unexplained 'name' parameter.

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 50%: only allow_downloads carries a description, and 'name' has no textual explanation, only regex/length constraints. The description's word 'Explicitly' hints at the required opt-in download authorization, but it does not explain name format, uniqueness, or that allow_downloads is pinned to true, so it only marginally compensates for the coverage gap.

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: 'provision a named canonical plugin's model'. That is concrete enough to distinguish it from read-only siblings like likenessforge_models and likenessforge_plugins, though 'canonical plugin' is jargon the agent must infer, and the name's 'download' framing versus the description's 'provision' framing is a minor mismatch.

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?

Gives the follow-up workflow explicitly ('poll danceflow_job_status') and points to danceflow_component for conditional effects, which is real usage guidance. It never says when to choose this over likenessforge_models or likenessforge_plugins, nor any precondition beyond the download authorization implied by 'Explicitly'.

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