openwebui_remove_file_from_knowledge

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

With no annotations provided, the description carries the full burden of disclosing behavioral traits. It explicitly states a key non-obvious behavior: the file itself is not deleted—only removed from this collection. This adds value beyond the tool name and covers the most important side-effect distinction. It doesn't mention other potential side effects (e.g., reversibility, permissions), but the statement is sufficient for the tool's scope.

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 with no wasted words. The first sentence states the core action, the second corrects a potential misconception and points to an alternative. Information is front-loaded and every sentence earns its place.

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 simple two-parameter mutation tool with no output schema and full schema parameter descriptions, the description is complete. It covers the tool's purpose, scope, and the key alternative. No critical information is missing.

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 covers 100% of parameters with clear descriptions ('File ID to remove from this collection', 'Knowledge base ID'). The description adds no additional parameter semantics beyond restating the collection context. Baseline 3 is appropriate because the schema already provides full parameter meaning.

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 states a specific action ('Remove a file from a knowledge base') and clearly distinguishes from the sibling tool by noting the file is not deleted, only removed from the collection. This differentiates it from openwebui_delete_file and mirrors the inverse of openwebui_add_file_to_knowledge.

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 explicitly tells when to use this tool vs. the alternative: 'Use openwebui_delete_file to delete the file entirely.' This provides clear usage guidance and prevents confusion between removal and deletion.

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