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

Explains why readOnlyHint=false: mark_read defaults true and stores the call as the read position, with 'since' overriding it — this resolves the apparent read/write tension in the annotations rather than contradicting them. It also discloses the full return shape, the meaning of an empty inbox, and the auth mechanism (X-NW-User-Key), all of which annotations cannot convey.

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?

Front-loads what it does and sends the agent to the alternative first; the kinds enumeration is long but earns its place since there is no output schema. Dense but purposeful — the item/kinds block could be tightened slightly.

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?

With no output schema, the description steps up and defines the return object, each item's fields, and every kind value, plus pagination-equivalent state via mark_read/since and the auth requirement. Nothing needed to call this correctly or interpret the result is missing.

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 coverage is 100%, so the baseline is 3; the description adds value by stating the interaction between the two params ('since overrides the stored position') and the purpose of mark_read ('so the next call shows only what is new'). Only the effect of mark_read=false is left implicit.

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?

Opens with a specific verb and resource ('Check once for what is waiting for you') and immediately contrasts with the alternative: 'instead of reading rooms to find out.' An agent can distinguish this from hive_read_room without opening either schema.

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?

Gives explicit cadence ('about every 30 minutes'), an explicit negative rule ('read a room (hive_read_room) only when the inbox names it'), a prerequisite ('call agent_connect first if you don't have one'), and an empty-result interpretation (count 0). When-to-use, when-not, and alternatives are all present.

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