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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and closed-world, so the safety profile is covered. The description adds useful scope context (user-uploaded or recorded assets only) and the returned field set, but says nothing about ordering, pagination, or how many items come back by default.

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 short sentences, resource first, no filler. The trailing 'addMedia op' reference is slightly cryptic since no such sibling tool appears in the toolset, but it costs little space.

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 annotations covering safety and no output schema, the description need not explain return values, but it should explain that 'kind' narrows results and that 'limit' caps them. Those omissions leave the two optional parameters effectively undocumented across both schema and description.

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 0%, so the description carries the burden and largely fails: neither the 'kind' filter (video/image/audio) nor 'limit' (1-200) is explained. The phrase 'Videos, images and sounds' loosely echoes the kind enum values but never indicates it is a filter parameter.

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 names the resource concretely ('Videos, images and sounds the user has uploaded or recorded') and enumerates the returned fields (id, name, kind, duration), so an agent knows exactly what this returns. It does not, however, explicitly differentiate itself from close siblings like view_media or get_media_levels.

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 only guidance is a forward reference to a downstream action ('Put one on the timeline with the addMedia op'), which is not a when-to-use rule. There is no statement of when to prefer this over view_media or the other media tools, and no mention of filtering or pagination behavior.

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