rag_chat

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

With no annotations provided, the description carries the full behavioral burden. It discloses that answers come 'with citations' and that the tool is a RAG chatbot, which is useful context beyond the name. However, it does not describe statefulness, how conversation history is handled, authentication needs, or whether it is read-only.

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 short sentences with no wasted words. The purpose is front-loaded and the second sentence adds the domain and return characteristic without redundancy.

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 description covers the basic purpose and citation behavior, but for a conversational tool with no annotations and no output schema, it lacks detail on how to manage multi-turn history (the 'history' parameter) or how top_k affects retrieval. It is minimally adequate but leaves notable behavioral gaps.

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 100%, so the schema already documents all three parameters (message, top_k, history). The description adds no additional meaning or usage guidance for any parameter, which is the baseline expectation when schema coverage is complete.

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 verb ('Chat', 'Ask questions') and resource ('Open5e RAG Developer Chatbot') and scope ('about Open5e API development'), and mentions the return type ('answers with citations'). It distinguishes itself from pure retrieval siblings like rag_search or rag_chunk by being conversational, but it does not explicitly name or differentiate from any sibling tool.

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 context 'Ask questions about Open5e API development' implies when to use this tool, but there is no explicit guidance on when to choose it over sibling tools such as rag_search, rag_chunk, or rag_sources. No exclusions or alternatives are stated.

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