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

With no annotations at all, the description must carry the safety profile, and it does disclose the key behavioral trait: this forces an immediate fetch rather than waiting for the scheduled round. It does not say whether the call blocks on the mail server, whether it has side effects or rate limits, or what happens on failure — meaningful gaps for an unannotated tool.

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 short sentences, zero filler: the mechanism ('right away instead of waiting for the next scheduled round') comes first and the invocation cue second.

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?

No output schema exists, so the description should carry more of the return contract than "answers with what came in" — it is unclear whether this yields full messages, headers, or just a count/notification. For a no-parameter polling tool with no annotations, the missing return shape and blocking/failure behavior leave it only minimally adequate.

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?

Zero parameters, so there is nothing for the description to compensate for; the baseline applies. The description correctly implies no arguments are needed.

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 concrete verb (reads/polls the account mailboxes) and a concrete effect: it bypasses the scheduled round and returns what arrived. That distinguishes it from a configuration-oriented sibling like list_mailboxes, but the description never names list_mailboxes or any sibling explicitly to draw the boundary.

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?

"Call it when you expect a message that has not appeared yet" gives a clear positive trigger. There is no explicit when-not guidance (e.g., don't poll in a loop, prefer list_conversations once mail is present), so the alternative-selection side is only implied.

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