anythingllm_list_documents_in_folder

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, covering the safety profile. The description adds minimal behavioral context beyond the folder scope, which is expected from the tool name. It does not contradict annotations and provides no additional traits like auth or rate limits.

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 concise and front-loaded, with a clear one-sentence purpose followed by a simple parameter explanation. Every word earns its place with no redundancy or filler.

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 low complexity (one parameter), rich annotations (read-only, idempotent), and presence of an output schema, the description is sufficient. It covers what the tool does, the parameter meaning, and the safety profile via annotations, making it complete for this simple 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?

The schema has no parameter descriptions (0% coverage), but the description includes an Args section explaining folder_name as 'Folder name to list documents from.' This adds meaningful semantics beyond the bare schema, effectively compensating for the lack of schema 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 tool lists all documents inside a specific folder, using a specific verb (List) and resource (documents in a folder). It distinguishes itself from sibling tools like anythingllm_list_documents, which presumably lists all documents without folder scoping.

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 for a specific folder via the phrase 'inside a specific folder,' but it does not explicitly state when to use this tool versus alternatives or provide exclusion criteria. No alternatives are mentioned, though the sibling list suggests a distinction.

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