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

Annotations only declare readOnlyHint=true and openWorldHint=false. The description adds real behaviour: results are ordered newest-first, carry status and output URLs, and render as an interactive panel in app-capable hosts with instructions not to duplicate its contents. It does not cover pagination or how status values should be interpreted, so it falls short of a 5.

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-loaded with the core scope before the routing note and the host-rendering instruction; every sentence serves a purpose. The inline list of all 14 type values duplicates the schema enum and slightly bloats the sentence.

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 and thin annotations, the description does useful work by naming the returned fields (status, output URLs) and the sort order, plus panel-rendering behaviour. The gaps are pagination semantics and status interpretation, which leaves it a step short of complete.

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 parameter meaning. It clarifies that 'type' selects one feature (though the enum values are already in the schema) but never explains 'page' or 'limit' — no mention of pagination, defaults, or the 100 cap. Two of three parameters are undocumented in both places.

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'), its ordering ('newest first'), and its payload ('status and output URLs'), then enumerates the supported feature types. It also explicitly routes uploaded files to the sibling list_uploads, so an agent can distinguish it from neighbours 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 an explicit use case ('find something made earlier — e.g. to post or reuse it') and names the alternative for a related need ('Uploaded files are in list_uploads'). It additionally states how to behave in app-capable hosts, which is directly actionable guidance.

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