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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered by structured data. The description's only added behavioral content is the default (60) and cap (1440) on the window, which is also present in the schema; it says nothing about how many messages come back, ordering, or what happens at the cap.

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?

A single sentence with zero filler, and the resource and the window constraint are both front-loaded. Nothing could be removed without losing 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 two-parameter read tool with rich annotations, the description is close to sufficient, but with no output schema it leaves the return shape unspecified — how many messages are returned, whether they are ordered, and whether there is any paging or truncation behavior. Those are the questions an agent would still have before calling it.

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%, so both parameters are already documented in the schema, and the description merely repeats the same default/max values for 'minutes'. Baseline 3 applies — no syntax, format, or edge-case meaning is added beyond the structured fields.

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?

States a specific verb and resource ('Get recent incoming messages') plus the scope ('last N minutes'), which is enough to separate it from the sibling whatsapp_last_outgoing_messages by direction. It stops short of explicitly naming that sibling, so differentiation is inferred from the word 'incoming' rather than stated.

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?

Usage is implied by the name and the time-window framing — an agent can guess this is the tool for polling recent inbound traffic — but there is no explicit when-to-use guidance, no exclusions, and no pointer to alternatives like whatsapp_get_chat_history or whatsapp_read_chat for older or per-chat retrieval.

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