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

Annotations already declare this a read-only, idempotent, non-destructive operation, so the safety profile is fully covered. The description adds ordering (newest first) and result content (unread counts, short preview), but an output schema exists, making that disclosure largely redundant. No pagination or limits are mentioned.

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 waste, front-loading the action and resource before the ordering and payload details. Nothing could be trimmed without losing 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?

Given a parameterless read tool with an output schema and rich annotations, the description covers the essentials an agent needs. The remaining gap is scope — whether 'the person's' means the caller or an arbitrary target — and any result-count limits, which keeps it from a 5.

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 and every property is documented at 100% coverage, so there is nothing for the description to compensate for. Baseline 4 applies; no parameter semantics are needed or expected.

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 (list) and resource (conversations) plus the ordering and payload (newest first, unread counts, short preview), so it is clearly distinct from single-item readers like read_conversation. It does not explicitly position itself against ambiguous siblings such as read_unread or pro_conversations, so it stops short of a 5.

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?

There is no when-to-use guidance, no stated prerequisites, and no mention of alternatives. The agent must infer from the name alone that this is the entry point for browsing conversations rather than reading one (read_conversation) or fetching unread items (read_unread).

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