Open WebUI MCP Server

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

With no annotations provided, the description carries full burden but only states the action without behavioral details. It doesn't disclose if deletion is permanent, reversible, requires specific permissions, affects related data, or has rate limits, leaving critical behavioral traits unspecified.

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 extremely concise with 'Delete a chat.', a single sentence that is front-loaded and wastes no words. While it may be overly brief for completeness, it earns full marks for conciseness and structure.

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 destructive tool with 1 parameter, 0% schema coverage, no annotations, and an output schema (though unspecified), the description is inadequate. It lacks details on behavior, parameters, and usage context, failing to compensate for the sparse structured data.

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%, with the single parameter 'chat_id' only labeled as 'Chat ID' in the schema. The description adds no meaning beyond this, failing to explain what a chat ID is, how to obtain it, or format requirements, leaving parameter semantics unclear.

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 'Delete a chat' clearly states the action (delete) and resource (chat), providing basic purpose. However, it doesn't differentiate from sibling tools like 'delete_all_chats', 'archive_chat', or 'delete_channel', leaving ambiguity about scope and alternatives.

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?

No guidance is provided on when to use this tool versus alternatives like 'delete_all_chats' or 'archive_chat'. The description lacks context about prerequisites, permissions needed, or what constitutes a deletable chat, offering minimal usage direction.

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