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

With no annotations, the description carries the full burden. It usefully discloses that the operation does not change the conversation's unread state, but it omits other behavioral details such as permission requirements, pagination behavior, or what a 'message' contains. The core non-mutation trait is covered, but not enough for a higher score without 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?

Two sentences, front-loaded with the primary action and key behavioral distinction, with no redundant or filler content. 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?

For a simple read tool with no output schema and full schema descriptions, the description is nearly complete: it covers the core action, the non-mutation guarantee, and a relevant alternative. It could optionally mention pagination or return format, but given the tool's simplicity, nothing critical 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 description coverage is 100%, so both parameters ('id' and 'limit') are already documented in the schema. The description adds no additional meaning or constraints beyond what the schema provides, so the baseline score of 3 applies.

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 states a specific verb ('Read') and resource ('latest messages of a conversation'), and it distinguishes the tool from siblings by noting it does not change the unread state (unlike inbox_mark_read/unread) and by pointing to agent_ask as the alternative for asking questions. This gives an agent immediate clarity on what the tool 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?

It clearly states the use case ('read the latest messages without changing unread state') and names an alternative ('use agent_ask... to ask about it'). However, it does not explicitly compare to inbox_list or state when not to use this tool, leaving some inference to the agent.

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