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 covered. The description adds valuable behavioral context by describing the returned document message fields (filename, content type, size, storage status, download availability) and the conditional follow-up, which goes beyond the annotations.

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 three sentences with no redundancy. It front-loads the core purpose, then adds relevant detail about document messages, and ends with a concise actionable instruction. Every sentence earns its place.

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 an output schema, so the description does not need to enumerate return fields. It covers the essential aspects: retrieving recent messages, document message attributes, and the download condition. The only gap is the unexplained parameter, which is minor given the tool's simplicity and the presence of a schema.

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 explain the parameter. It does not mention conversationId at all, leaving its meaning and origin implicit. The single parameter is simple, but the description adds no value beyond the schema's property name, failing to compensate for the missing schema description.

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 retrieves a single WhatsApp conversation and its recent messages, with a specific verb and resource. It also distinguishes from the sibling list_whatsapp_conversations by implying a singular focused retrieval rather than a listing, and adds detail about document message fields.

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 gives a clear follow-up action for document downloads ('Use download_whatsapp_document...') but does not explicitly contrast when to use this tool versus alternatives like list_whatsapp_conversations. It implies usage for fetching a specific conversation's details, but leaves the selection criteria unstated.

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