client_getChats

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

With no annotations provided, the description must carry the full burden of behavioral disclosure, but it only states the basic retrieval action. It does not explicitly confirm that the operation is read-only, mention potential for large result sets, or describe behavior on invalid session IDs. The word 'get' implies reading, but this is not explicit.

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 two short sentences, with the first sentence front-loading the core purpose. The second sentence adds the session ID requirement, though it is slightly redundant with the first. Overall, it is appropriately sized and easy to parse.

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?

This is a simple tool with one parameter and no output schema, so the description should explain what the tool returns. It states that it retrieves all chats, but it doesn't describe the return format or potential pagination. While the purpose is clear enough for basic selection and invocation, the lack of return details makes it only moderately complete.

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 provides 100% description coverage for the only parameter, sessionId, including an example. The tool description reiterates the session ID context but adds no meaning beyond what the schema already provides, so the baseline score of 3 is appropriate.

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: "Get all current chats" and "Retrieve all chats for the given session ID." It specifies a distinct resource and scope, and the phrase "all current chats" differentiates it from siblings like client_getChatById and client_getChatsByLabelId.

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 through its name and phrase "all current chats," but it does not explicitly provide when-to-use/when-not-to-use guidance or name alternative tools. The mention of "for the given session ID" gives a prerequisite, but no exclusions or sibling comparisons are provided.

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