waha_get_messages

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

With no annotations provided, the description carries the full burden of behavioral disclosure. However, it only says 'Get messages from a chat' and does not detail side effects, media handling, pagination, or read receipts. The description offers minimal transparency beyond the basic read operation.

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 a single, concise sentence ('Get messages from a chat') with no filler words. It front-loads the action and every word earns its place, achieving high conciseness.

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, and the description does not explain return formats, chatId format, message types, or filtering options. Although the schema provides some parameter details, the overall completeness is insufficient for an agent to fully understand the tool's behavior without additional context.

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 schema already describes 67% of parameters (limit, downloadMedia) with defaults, and the description adds no parameter-specific information. Since schema coverage is high, the baseline of 3 is appropriate; the description provides no additional semantics.

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 with a specific verb ('Get') and resource ('messages from a chat'). It is distinct from sibling tools like waha_get_chats or waha_send_text, making its 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 its usage (retrieval of messages) but provides no explicit when-to-use guidance, exclusions, or alternatives. It does not mention when to prefer this over waha_get_chats or other related tools, leaving the context inferred.

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