anythingllm_create_folder

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

Annotations are all false (not read-only, not idempotent, not destructive), providing no useful behavioral information. The description adds nothing beyond the basic action, omitting details like duplicate folder behavior, side effects, or permission requirements. The agent is left without critical safety or execution 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 extremely concise, using a single sentence and a simple arg list. It is front-loaded with the core purpose and contains no fluff. For such a simple one-parameter tool, this size is appropriate.

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?

Despite the tool's simplicity, the description leaves significant context gaps. It does not explain what 'document folder' means in the AnythingLLM context, whether it is scoped to a workspace, or what happens if a folder with the same name exists. The output schema exists, so return values are covered, but the operational context 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 input schema has one required parameter 'name' with no schema-level description (0% coverage). The description compensates minimally by saying 'name: Name for the new folder,' which clarifies the parameter's purpose but adds no constraints or additional meaning. It meets the baseline but does not enrich the semantics beyond what the parameter title implies.

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 tool's purpose: 'Create a new document folder in AnythingLLM.' This is a specific verb+resource construction that unambiguously identifies the action. It does not explicitly distinguish from sibling tools like create_workspace, but the resource 'folder' is distinct enough to avoid confusion.

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 no guidance on when to use this tool versus alternatives. It does not mention any prerequisites, exclusions, or relationships to sibling tools such as remove_folder or list_documents_in_folder. There is no context to help an agent decide if this is the right tool.

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