whatsapp_get_messages

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

With no annotations, the description must disclose behavioral traits, but it only mentions 'buffered' and 'newest first'. It does not explain whether messages are consumed (removed) after retrieval, which is critical for a buffered message tool. No information about rate limits, pagination, or empty-buffer behavior is provided.

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, front-loaded sentence that communicates purpose and core options without filler. Every word contributes value, and the structure is ideal for quick understanding.

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 tool has no output schema and no annotations, so the description should cover return value format and behavioral side effects. It mentions filtering and ordering but omits what the returned message objects look like and whether the buffer is drained. This leaves important gaps, though the core filtering logic is clear.

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 coverage is 100%, so each parameter already has a description. The tool description merely rephrases the filter options ('chatId', 'since', 'limit') without adding extra semantics like value formats or interaction effects. This meets the baseline for high schema coverage.

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 starts with a clear verb and resource: 'Get buffered incoming messages' and specifies ordering ('newest first'). This distinguishes it from sibling tools like whatsapp_send or whatsapp_list_chats, which are about sending or listing chats.

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 clearly implies when to use it: retrieving buffered incoming messages. It does not explicitly exclude alternatives, but the context is unambiguous since the sibling tools have different purposes. The absence of exclusions is acceptable for a straightforward read tool.

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