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

Goes well beyond the annotations, which only declare it is not read-only, idempotent, or destructive. The description adds cost (free), a quota ("A few previews per Remake and per day"), and a consent requirement for real people, all of which change how an agent should call it. It stops short of describing the returned preview artifact.

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?

Front-loaded with the key fact ("Free:") and kept to three sentences with no filler. The final sentence is dense but each clause carries operative constraints (consent, rate limit, argument reuse).

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?

Covers cost, quota, consent/legal prerequisites, and argument compatibility for a low-risk generation call, which is enough for correct invocation. With no output schema, the description leaves the returned frame's format unspecified, which is the only real gap.

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 100%, so the baseline is 3, but the description adds genuine cross-tool semantics: cast/performers take the same shape as in remake_render, so an agent can reuse a payload rather than re-deriving it. The approval_id consent flow is left to the schema.

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 artifact ("draws the Remake's opening frame with the chosen cast") and names the sibling it precedes (remake_render), so an agent can distinguish it from the paid render step without reading either schema.

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?

"before paying for remake_render" gives a clear selection context versus the render sibling, and "Takes the same cast or performers as remake_render" tells the agent it can reuse arguments. It does not state explicit when-not conditions, but the sequencing plus quota note makes usage unambiguous.

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