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 full burden for behavioral disclosure. It states 'Get folder details' but offers no information on permissions required, rate limits, error conditions, or what the output contains. This is inadequate for a tool that likely returns structured data about a folder.

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 at three words, with no wasted language. It is front-loaded with the core action, though this brevity contributes to underspecification rather than clarity.

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 no annotations, 0% schema description coverage, but an output schema exists, the description is incomplete. It does not hint at what details are returned or contextualize the tool's role among siblings. The output schema may cover return values, but the description lacks basic operational context.

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 'folder_id' documented only as 'Folder ID' in the schema. The description adds no meaning beyond this, failing to explain what a folder ID is, where to find it, or format requirements. With low coverage, the description should compensate but does not.

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 'Get folder details' restates the tool name 'get_folder' in slightly different words, making it tautological. It provides a basic verb+resource combination but lacks specificity about what details are retrieved or how it differs from similar tools like 'list_folders' or 'update_folder'.

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. With siblings like 'list_folders' (for listing multiple folders) and 'update_folder' (for modifying folders), the description fails to indicate that this tool is for retrieving details of a specific folder identified by ID, leaving usage context ambiguous.

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