read_group_messages

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

The word 'read' implies a non-destructive, read-only behavior, which is useful context. However, with no annotations, the description carries the full burden and does not disclose other behavioral traits like ordering of messages, rate limits, or whether any special permissions are required.

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 directly states the purpose. No wasted words or redundant information.

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?

For a simple read tool with two parameters and no output schema, the description combined with the schema is adequate. It clearly conveys the tool's purpose and the limit parameter implies how 'recent' is quantified. Minor gaps like return format or ordering are not critical for this simplicity level.

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?

Both parameters are fully described in the schema (100% coverage), with groupName being self-explanatory and limit described as 'Number of recent messages to read'. The description adds no extra meaning beyond what the schema already provides.

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 action ('Read') and resource ('recent messages from WhatsApp group'). It distinguishes itself from the sibling tool 'send_group_message' by being a read operation, which is a natural differentiator.

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?

No guidance is provided on when to use this tool versus alternatives. While the name and description imply it's for reading messages, it does not explicitly mention when to use it instead of send_group_message or other tools.

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