Open WebUI MCP Server

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions 'ADMIN ONLY', indicating authentication needs, but doesn't describe what 'Export' entails (e.g., format, scope, whether it's a read-only operation, potential side effects like file generation, or rate limits). For a tool with zero annotation coverage, this leaves significant gaps in understanding its behavior.

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 just two phrases: 'Export full system configuration. ADMIN ONLY.' Every word earns its place by stating the action, resource, and a key constraint, with no wasted information. It's front-loaded and efficiently structured.

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 that there are 0 parameters, schema description coverage is 100%, and an output schema exists, the description doesn't need to cover inputs or return values. However, as a configuration export tool with no annotations, it should provide more behavioral context (e.g., output format, admin requirements details). The description is minimal but adequate for the low complexity, though it could be more 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 input schema has 0 parameters with 100% description coverage, so no parameter information is needed. The description doesn't add any parameter details, which is appropriate here. A baseline of 4 is applied since there are no parameters to document, and the description doesn't introduce confusion or redundancy.

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 ('Export') and resource ('full system configuration'), making the purpose specific and understandable. However, it doesn't explicitly distinguish this tool from sibling tools like 'get_system_config' or 'get_models_config', which might also retrieve configuration data, so it misses full sibling differentiation.

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 includes 'ADMIN ONLY', which provides implied context about when to use this tool based on user permissions. However, it lacks explicit guidance on when to choose this over alternatives like 'get_system_config' or other configuration-related tools, and doesn't mention any exclusions or prerequisites beyond admin access.

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