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

Annotations cover the safety profile (readOnlyHint=true, openWorldHint=false), and the description adds genuinely non-obvious behavior: in app-capable hosts the result renders as an interactive panel the user sees and acts on, which drives the 'do not repeat contents' instruction. It omits any mention of rate limits, ordering, or what happens across hosts that lack app support, so it is good but not exhaustive.

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, front-loaded with the resource definition before the host-dependent behavior and the output-handling rule. Every sentence earns its place; the middle sentence is dense but not padded.

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 no output schema, the description correctly explains how results surface (an interactive panel) and how the agent should respond, which is the key missing structured information. However, pagination semantics for page/limit are left entirely unexplained, leaving a real gap for a tool whose only parameters are those two.

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% and the two parameters (page, limit) are undocumented in both schema and description — notably the limit maximum of 100 and any default page size. With two non-trivial pagination params the description is expected to compensate and it says nothing about them.

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 uploaded media assets' — and distinguishes it from sibling list tools (list_generations, list_posts) by naming the exact asset class and its origin (upload_file or the app). It stops short of explicitly naming the sibling it is not, so it is clear but not fully differentiated.

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 context for when this tool is the right call: in hosts that show apps, invoking it is how the user uploads a file, and the agent should direct them to the panel's Upload button. It also states a usage constraint (do not restate panel contents). It does not contrast against upload_file or create_upload_url, which limits 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.