waha_list_chats

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

No annotations are provided, so the description carries the full burden. 'List' plus 'newest first' does convey read-only semantics and result ordering beyond the schema, but it says nothing about pagination behavior, what happens with an invalid/inactive session, or result limits relative to the limit param.

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?

A single tight sentence with the key ordering fact front-loaded, no filler. It is arguably under-specified rather than verbose, but nothing in it is wasteful.

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?

With zero schema coverage, no annotations, and three parameters, the definition leaves an agent guessing about limit/offset semantics and session preconditions. The existence of an output schema covers return values, but the call-side gaps remain substantial.

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 and mostly does not: 'for a session' weakly covers the required session param, while limit and offset receive no explanation of their meaning, defaults, or pagination interaction.

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+resource ('List recent chats') and scopes it to a session, with ordering ('newest first') clarified. It is distinguishable from waha_get_chat and waha_get_chat_messages by implication, but it never explicitly names those siblings.

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?

There is no statement of when to use this vs. alternatives (e.g., waha_get_chat_messages for message content, waha_get_chat for a single chat), and no prerequisites such as whether the session must be started first.

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