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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description usefully adds result ordering ('newest first') and that results span web and app sessions, but says nothing about pagination behavior, result volume, or what an offset beyond the range does — for a paged list tool that is a real gap.

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 sentence with zero filler, and the most important facts — recency ordering and cross-platform scope — are front-loaded.

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?

An output schema exists, so return values need not be described, and annotations cover the safety profile. What's left thin is paging guidance (an agent can't tell how to iterate offset) and any hint about typical result counts, but for a simple read-only list tool this is nearly sufficient.

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 67%: limit (max 50, default 20) and media (image/video enum) are well documented, while offset has no description at all. The description adds nothing about filtering or paging semantics, so the undocumented offset parameter remains unexplained in both places.

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 the user's recent image and video tasks') plus ordering ('newest first') and scope ('ones made on the web or in the app'). It is clearly different from get_tasks by being a recency listing rather than an ID lookup, though it never names that sibling explicitly.

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 by 'recent' and the media filter, but there is no explicit when-to-use or when-not-to-use guidance relative to get_tasks or the create/generate tools. An agent must infer that this is the discovery entry point for past work.

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