openwebui_list_chats

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

With no annotations provided, the description carries the burden. It discloses that it returns up to 50 chats per page and the fields (title, ID, last update time), giving a clear picture of the output. It does not mention potential caveats like whether it only returns metadata, but for a list operation the behavior is well conveyed.

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?

The description is two sentences, front-loads the verb and resource, and every sentence adds information - the page size, return fields, and pagination instruction. No fluff.

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?

For a simple listing tool with one parameter and no output schema, the description gives enough to understand the return payload and pagination. It lacks mention of how to get full chat contents, but that is a separate tool. Given low complexity, it is nearly 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?

The schema already fully documents the page parameter with default and description, so the baseline is 3. The description adds value by stating the per-page limit of 50 chats, which is not in the schema, and explicitly connects the page parameter to pagination.

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 uses the specific verb 'List' and names the resource 'chat conversations in Open WebUI', clearly distinguishing it from sibling tools like search or get. It also specifies scope with 'recent' and return fields, making the purpose unambiguous.

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 description provides the main usage context (listing recent chats) and instructs to use the page parameter for pagination, but does not explicitly mention alternatives such as openwebui_search_chats for searching or openwebui_get_chat for retrieving a single chat. Thus it lacks explicit when/when-not guidance.

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