anythingllm_get_thread_chats

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds no additional behavioral context beyond the obvious read operation, such as what data is returned or any constraints (e.g., requires existing workspace/thread). It simply restates the read nature without enriching the agent's understanding.

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: a single sentence stating the purpose, followed by a clean two-bullet args list. No filler, no redundancy, and the key information is front-loaded. Every word 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 read-only tool with two parameters, annotations covering safety, and an output schema present, the description is mostly complete. It covers purpose and parameter meaning, but lacks explicit usage alternatives and potential edge cases (e.g., thread not found). Given the tool's simplicity, the minor gaps are acceptable, but not perfect.

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%, so the description must compensate. It adds brief definitions for both parameters ('slug: Workspace slug', 'thread_slug: Thread slug'), clarifying the ambiguous property names. However, it provides no format, validation rules, or guidance on how to obtain these values, so it only partially compensates.

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 ('Get chat history') and the specific resource ('a specific thread in a workspace'). It distinguishes from the sibling `anythingllm_get_chat_history` by explicitly narrowing to thread-level history, making the tool's purpose unambiguous.

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 context by mentioning 'specific thread in a workspace', but it does not explicitly state when to choose this over alternatives like `anythingllm_get_chat_history` or `anythingllm_chat_in_thread`. No when/when-not guidance is given, so it barely meets the 'implied usage' level.

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