Recent video jobs

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

Annotations already declare readOnly/idempotent/openWorld, so the bar is lower, and the description adds real return-content context (status, clips, and credit balance) that no output schema provides. It also explains the effect of completedOnly ('skip anything still rendering'), though it says nothing about ordering, recency window, or the default page size.

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?

Two tightly written sentences: the primary purpose and payload are front-loaded, and the optional filter is mentioned last. No filler or repetition.

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?

With no output schema, the description usefully summarizes the return payload, and all parameters are covered by the schema. Minor gaps remain: no recency window, default limit, or ordering behavior for a list that could be long.

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 100%, so all three parameters are already documented; the description only restates completedOnly as 'skip anything still rendering,' which adds little beyond the schema's 'Only return finished jobs.' Baseline 3 applies when the schema does the heavy lifting.

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 states a specific verb+resource ('Recent video generations in this workspace') and even names the payload (status, clips, credit balance), so it is clearly a listing tool. It never names the sibling get_video_job, so an agent must infer the list-vs-single distinction from the plural phrasing rather than being told.

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?

Usage is implied ('recent generations ... plus the credit balance') and the completedOnly note gives a concrete filtering scenario, but there is no explicit when-to-use, when-not-to-use, or pointer to get_video_job for a single job. Adequate but leaves routing to inference.

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