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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds real value beyond that by disclosing return content (per-status counts and an array with id, status, prompts, model, ref counts, scheduledAt, finishedAt) and the default recency window.

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 dense sentences, zero filler, with the primary scope stated first and the sibling disambiguation last. Every clause carries information about scope, contents, or alternatives.

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, so the description usefully summarizes the response shape and counts; it also clarifies default recency behavior. It leaves minor gaps such as pagination or whether counts are affected by the limit/status filter, but an agent has enough to call it correctly.

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 limit and status are already documented with defaults and the enum array form. The description only implies status grouping via 'counts per status' and adds no syntax or filtering semantics 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 (list picture generations) and narrows scope to 'recent and active: queued batches and the pictures generate_image made right in the chat'. It explicitly routes videos and audio to sibling tools, so an agent can distinguish this from list_my_videos/list_my_audio without opening a 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?

The description names the alternatives for other media types (list_my_videos, list_my_audio) and defines the default view as 'active + recent', which tells the agent when this tool applies. It does not, however, contrast with sibling lookups like show_generation or status tools, and gives no explicit when-not guidance.

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