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. It clearly discloses the irreversible destructive nature ('Cannot be undone!'), which is crucial behavioral context for a deletion tool. It doesn't mention permissions, rate limits, or response format, but the warning adequately covers the primary risk.

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?

Two sentences total: the first states the purpose, the second provides critical warning. Both sentences earn their place with zero waste, and the warning is appropriately front-loaded for immediate visibility.

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 0-parameter destructive tool with no annotations but an output schema, the description provides sufficient context: clear purpose, irreversible warning. It doesn't need to explain return values (output schema covers that) or parameters. The only minor gap is lack of explicit permissions or confirmation details.

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 tool has 0 parameters with 100% schema description coverage, so no parameter documentation is needed. The description appropriately doesn't discuss parameters, maintaining focus on the tool's purpose and warning.

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 clearly states the action ('Delete') and resource ('all your chats'), with specific scope ('all') that distinguishes it from sibling tools like delete_chat (singular). It provides a complete verb+resource+scope combination without tautology.

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 implies usage context through the warning ('WARNING: Cannot be undone!'), suggesting this is for irreversible bulk deletion. However, it doesn't explicitly state when to use this vs. alternatives like delete_chat or provide specific prerequisites or exclusions.

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