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 states this is a creation operation, implying mutation, but doesn't disclose behavioral traits like required permissions, whether duplicates are allowed, what happens on success/failure, or any rate limits. The mention of 'triggered by a command' adds minimal context.

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 a single, efficient sentence with no wasted words. It's front-loaded with the core purpose and includes a useful contextual detail about command triggering.

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 has an output schema (which handles return values) but no annotations and 0% schema description coverage, the description is minimally adequate. It states the basic purpose but lacks details on usage context, parameter meanings, and behavioral expectations for a mutation tool.

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%, but the description doesn't add any parameter information beyond what's implied by 'triggered by a command' (hinting at the 'command' parameter). It doesn't explain the three required parameters (command, title, content) or their relationships, leaving significant gaps despite the schema having no descriptions.

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 ('Create a new prompt template') and the resource type ('prompt template'), which distinguishes it from siblings like 'create_note' or 'create_tool'. However, it doesn't specify what distinguishes it from 'update_prompt' or what makes a 'prompt template' unique in this system.

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 mentions the tool is 'triggered by a command', which provides some context about when it might be used, but offers no explicit guidance on when to use this versus alternatives like 'update_prompt' or 'create_function', nor does it mention prerequisites or exclusions.

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