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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint, so the safety profile is covered. The description adds only the 'cheap check' framing and a pointer to `say` for the readable summary, without disclosing what get_unread itself returns (count, boolean, list) or any auth constraint.

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 relevant content is front-loaded in the first two sentences, but the remainder is off-topic vendor boilerplate about job listings and references a `say` tool not present among siblings. Those sentences do not earn their place and crowd out genuinely useful 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 zero-param read tool with no output schema, the description should say what an agent gets back (unread count vs. messages vs. a redirect to `say`). It hints the summary lives in `say` but never clarifies get_unread's own return, and the job-listing text is irrelevant to the tool's role.

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?

The tool takes zero parameters, so there is no parameter semantics to explain; the baseline of 4 applies. The description adds nothing here, which is acceptable given the empty schema.

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 first two sentences ('Any unread messages? A cheap check') convey the core purpose, but they largely restate the name/title and offer no differentiation from siblings like get_inbox or get_hiring_inbox. The bulk of the description then pivots to unrelated job-listing messaging, muddying rather than sharpening what this tool actually does.

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?

'A cheap check' implies this is a lightweight alternative to fetching full messages, which weakly suggests when to use it. But no alternative is named (the referenced `say` is not a sibling), there are no explicit when/when-not conditions, and no prerequisite guidance.

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