List media this app uploaded

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

Annotations already declare read-only, idempotent, and non-destructive behavior. The description adds useful behavioral context beyond that: only app-uploaded media is returned, results are newest-first, and album scoping is optional, with no contradictions.

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 short sentences front-load the core purpose and scope, then provide the alternative and pagination. Every sentence carries distinct useful information with no repetition.

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?

The description is complete for a filtered read-only listing tool: scope, ordering, pagination, and routing to the appropriate sibling are all present. The rich annotations and fully described schema cover the remaining safety and parameter context.

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?

All four parameters are fully documented in the schema, so the description does not need to add parameter-level detail. It slightly reinforces album scoping and pagination but adds no semantics beyond the schema.

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?

Description names the resource (media items), action (List), ordering (newest first), and scope (this app's uploads, optionally one album). It also explicitly contrasts with start_pick_session, so an agent can distinguish it from the closest sibling.

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?

States when to use it (listing this app's uploads) and when not ('To reach anything else in the user's library, use start_pick_session'). The pagination note gives a concrete operational instruction for continuing results.

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