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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds only "recent," implying recency-ordered results, but says nothing about ordering direction, default limit behavior, or result shape. Adequate but thin given the annotations do most of the work.

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?

A single front-loaded sentence with no wasted words. Efficient, though its brevity borders on under-specification rather than crispness.

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 should convey return shape/ordering, and it doesn't. Combined with undocumented `limit` and `status` parameters, the definition is too sparse for an agent to invoke confidently beyond the basics.

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 only 33%: the `before` cursor is well documented in the schema, but `limit` and the `status` enum carry no descriptions anywhere. The description adds zero parameter meaning (e.g., default page size or what status values filter on), so it fails to compensate 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 ("List") and a clear resource ("image, video, and talking-head generation jobs"), which lets an agent distinguish it from get_studio_generation (single item) and list_studio_models (models, not jobs). No explicit sibling naming, but the resource scoping is unambiguous.

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?

The description gives no when-to-use context: it doesn't say to use this instead of get_studio_generation for a single job, doesn't mention pagination workflow, and doesn't explain the status filter's purpose. The agent must infer all routing from the tool name alone.

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