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

Annotations already cover readOnly/idempotent/non-destructive, but the description adds behavior they cannot express: long videos take minutes and the caller should re-poll after a short wait, cancellation is not possible from this tool, and the response carries status, progress, and error plus the resulting project_id or clip_ids. The polling/latency guidance is the single most important operational detail for this tool and it is stated plainly.

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 front-loaded with the user-intent triggers, then parameters, returns, caveats, exclusions, and next steps in a scannable order. It runs a bit long and the phrase "Free and read only" partly restates the readOnlyHint annotation, but no sentence is genuinely wasted.

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?

For a single-parameter polling tool with an output schema and full annotations, nothing an agent needs is missing: what triggers it, what ID to pass and where it comes from, expected latency and re-polling, what comes back, what it cannot do, and which tool to call next.

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 0% (job_id has no description), so the description must carry the weight, and it does: it explains that job_id is the identifier returned by any of eight named producing tools. It does not specify the ID's format, but the provenance list is exactly the meaning an agent needs to source the value correctly.

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 names a specific verb+resource (poll the status of a RipClip job) and grounds it in concrete user phrasings ("is my import done", "are my clips ready", "did the edit render"). It also enumerates which sibling tools produce job_ids, making it unmistakable which tool this is versus get_moments or list_clips.

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 gives explicit when-to-use triggers, an explicit when-not-to-use clause (not for cancelling or changing a job, since that is impossible here), and redirects to get_moments for reading a find_moments result. It even supplies follow-up routing (estimate_hu after import; list_clips/explain_clips/preview_frame after clips or an edit), which is more than most definitions offer.

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