post_client_getChats

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

No annotations are provided, so the description must disclose behavioral traits. It only states the action (get all chats) without mentioning side effects, permissions, rate limits, pagination, or whether the session must be active. This is a significant gap for an unannotated read tool.

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 (two sentences) but redundant: 'Get all current chats with optional search parameters' is nearly repeated in the second sentence. It is front-loaded with the core action, but the repetition wastes words without adding significant value.

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?

There is no output schema, so the description should explain what the tool returns (e.g., array of chat objects, count, pagination). It only says 'Get all current chats' without any return details. Given the low complexity and absence of annotations, the description is incomplete for an AI agent to fully anticipate the tool's behavior.

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 description says 'optional search parameters' but does not name them, leaving ambiguity about what filters exist. The schema already documents sessionId, since, and unread, so the description adds little value beyond the structured data. With only 50% schema coverage, the description should compensate but does not.

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 retrieves all chats for a given session ID, using the verb 'Get' and specifying the resource 'chats'. It distinguishes from siblings like client_getChatById (single chat) and client_getChatsByLabelId (by label) by emphasizing 'all' and 'given session ID', though it does not explicitly name these alternatives.

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 provides clear context: use this to list all chats for a session, with optional search parameters. It implies the tool is for broad retrieval rather than specific lookups, but it does not explicitly mention when not to use it or name alternative tools.

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