Open WebUI MCP Server

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It adds value by stating 'Removes all users from the group', which clarifies the destructive impact beyond just deletion. However, it lacks details on permissions, rate limits, or response behavior, leaving gaps in transparency for a mutation tool.

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 two sentences that are front-loaded and waste no words. Every part ('Delete a group', 'ADMIN ONLY', 'Removes all users from the group') earns its place by conveying essential information efficiently.

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?

Given the tool's complexity as a destructive mutation with no annotations, the description is partially complete: it covers purpose, admin requirement, and behavioral impact. However, with an output schema present, it doesn't need to explain return values, but it still lacks parameter details and full behavioral context, making it adequate but with gaps.

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 description coverage is 0%, and the description doesn't mention the 'group_id' parameter at all. It fails to add any meaning beyond what the bare schema provides, such as explaining what a group ID is or how to obtain it, which is insufficient given the low coverage.

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 verb ('Delete') and resource ('a group'), making the purpose specific and understandable. However, it doesn't explicitly differentiate from sibling tools like 'delete_user' or 'delete_all_chats', which would require mentioning it targets groups specifically versus other entity types.

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 clear context with 'ADMIN ONLY', indicating when to use this tool based on user permissions. It doesn't specify alternatives or exclusions, such as when to use 'update_group' instead for modifications or 'delete_user' for different entities, but the admin constraint is a strong usage guideline.

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