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

Annotations already declare readOnlyHint and destructiveHint=false, so the description does not need to restate safety; instead it adds real behavioral value the annotations lack — the newest-first ordering and the distinction between durable 'assets[].file_path' and 'temporary signed URLs' for preview/download, which signals URL expiry. It stops short of saying how long URLs live.

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?

Three sentences, all load-bearing: scope and ordering first, output-shape guidance second, pagination/safety last. No filler or restatement of the title.

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 needn't be spelled out, yet the description still notes where reusable file paths live and that signed URLs are temporary — exactly the practical details an agent would otherwise get wrong. Nothing needed to call this correctly is missing.

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 100%, so the baseline is 3; the description earns a bump by documenting the cross-field relationship between the response's next_cursor and the cursor parameter, which the schema alone does not convey.

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 (lists) and resource (saved items), enumerates the five item types returned, and specifies ordering ('newest first'). No sibling tool lists saved items, so this is unambiguous against the surrounding generate/edit/fetch tools.

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?

Gives clear operating context: read-only, newest-first, and explicitly how to paginate ('pass next_cursor as cursor for the next page'). It does not name an alternative tool or state when-not to use this one, which keeps it below a 5.

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