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

Annotations cover the safety profile (readOnlyHint=true, openWorldHint=false), but the description adds real non-obvious behavior: results are ordered newest first, each entry carries status and output URLs, and in app-capable hosts the output renders as an interactive panel that must not be duplicated in the reply. Return-content shape and host-dependent rendering are disclosed, which is beyond what the annotations provide.

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?

Front-loads what the tool does and its scoping, then adds routing and host-behavior notes in short sentences. The long embedded enum list is somewhat bulky but matches the schema's values, and every remaining sentence carries actionable information.

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 compensates by naming the returned fields (status, output URLs) and the ordering, plus the panel-rendering caveat. For a read-only list tool this is a complete picture of what an agent needs to call and report it correctly; only paging semantics remain unaddressed.

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 must carry the parameter burden, and it does not: 'page' and 'limit' (max 100) are never explained, and pagination behavior is unstated. The type enum values are simply re-listed, which duplicates the schema rather than adding meaning; only 'for one feature' hints at scope.

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 ('Browse the user's past results for one feature') and scopes it by enumerating the exact feature types the tool covers. It also distinguishes itself from the sibling list_uploads by explicitly saying uploaded files live there, letting an agent route correctly without opening a schema.

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 a clear use case ('find something made earlier, e.g. to post or reuse it') and names one alternative (list_uploads) for a related but distinct resource. It does not, however, say when to prefer this over single-item status tools like image_status or video_status, so the routing guidance is incompletely bounded.

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