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

Despite annotations covering safety, the description adds substantial behavioral context: cost model (~1.2x a straight 1080p render, billed on top of the draft), a 7-day validity window with refusal after expiry, idempotent double-call behavior that charges nothing the second time, and a no-polling contract. These go well beyond idempotentHint/openWorldHint.

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-loads the core action in the first clause, then layers billing, validity, idempotency, and polling rules. It is long but every sentence is actionable and nothing is redundant filler, which is appropriate given the billing and workflow complexity.

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?

No output schema exists, yet the description covers return behavior (interactive self-refreshing result card), error/expiry behavior (7-day refusal), and side effects (charges, no re-roll). An agent has everything needed to call this correctly and to instruct the user.

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% and both parameters (generation_id, get_cost) are already fully documented in the schema, including the get_cost non-submitting semantics. The description restates the generation_id source and the quote-without-submitting behavior but adds no syntax, format, or edge-case detail beyond the schema. Baseline 3 applies.

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 ('Render the 1080p final from a ... DRAFT') and pins its scope as 'the second and last step of draft mode.' It implicitly distinguishes itself from popcraft_generate_video and popcraft_upscale_video by naming the draft workflow, and explicitly says it does NOT re-roll the clip.

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 an explicit precondition ('only take this step once the user has SEEN and approved the preview'), an explicit alternative for progress checks ('call popcraft_job_display at most once, and only if no card rendered'), and a when-not (never quote generation time). Routing is unambiguous.

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