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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is known. The description adds the 'recent message history' qualifier, which gives some behavioral insight into the return scope, but does not describe limits, pagination, or authentication requirements. Given annotations cover safety, a 3 is appropriate.

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?

Two sentences with no waste. The primary action is stated first, followed by concrete use cases. Every word earns its place, and the description is front-loaded.

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 detailed schema and safety annotations, the description is nearly complete. It states the action and purpose, and the schema covers parameters. The only minor gap is not specifying exactly what 'recent' means, but this is not critical for correct invocation.

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 100% with detailed explanations for both chat_id and account_id, including what not to pass and how to resolve the account. The description adds no parameter-specific info beyond the schema, so baseline 3 is correct.

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 and resource: 'Read a WhatsApp chat and recent message history.' It is clear and distinct from generic messaging tools like messaging_list_messages, and the use cases (context, summaries, follow-up detection, cross-channel workflows) clarify its role in the conversation lifecycle.

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 when-to-use context: before sending a reply, for context and summaries. It does not explicitly name alternatives or exclusions, but the intended workflow is evident. Since there is no competing WhatsApp read-conversation tool among siblings, the guidance is sufficient.

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