anythingllm_remove_folder

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

The description adds meaningful behavioral context beyond the annotations by noting the deletion is 'permanent' and includes 'all its contents.' This explicitly discloses the destructive scope and irreversibility, which is particularly valuable since the annotation already marks destructiveHint=true. No contradictions exist.

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 one sentence for the main function and one line for the parameter explanation. It is front-loaded with the critical information and contains no extraneous content.

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?

The tool is simple with a single parameter, an output schema, and annotations indicating destructive behavior. The description fully explains what is deleted and the parameter meaning, making it complete for an agent to select and invoke without ambiguity. No additional prerequisites or return-value details are necessary given the output schema.

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 provides no description for the single parameter 'name', but the description compensates with 'Args: name: Folder name to delete.' This clarifies the parameter's meaning and purpose, though it does not add formatting or constraint details. Given the schema coverage is 0%, the description does adequately compensate for the one parameter.

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 function: 'Permanently delete a document folder and all its contents.' This provides a specific verb (delete) and resource (document folder) while also distinguishing from related tools like remove_documents (which deletes documents, not folders) and create_folder (which creates, not deletes). The scope of deletion (including contents) adds clarity.

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 implies usage in that this tool is for deleting a folder, but does not explicitly state when to use it versus alternatives. No exclusions or alternative tool mentions are given. The implied usage is straightforward, so it sits at 'implied usage' rather than 'no guidance'.

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