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

The description adds meaningful behavior beyond the annotations: the server persists the read cursor and current time, so the agent should not compute them, and the five returned buckets are all described. This is consistent with readOnlyHint=false and idempotentHint=false (the call advances server-side read state), with no contradiction.

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 when-to-call instruction is front-loaded, followed by a compact enumeration of returned fields, with no filler. The parenthetical field glosses are dense but each earns its place by defining the return shape given there is no output schema.

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 fully compensates by defining each of the five returned fields and clarifying that read position and time are server-managed. An agent has everything needed to call it and interpret the result.

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% and the single parameter my_room is documented in the schema itself as the room name exactly as written in project instructions. The description adds no further detail about the parameter, so the baseline 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 names a specific action (call first at session start) and enumerates exactly what is returned (new_posts, waiting_on_you, replies_to_you, pins, now_kst), so an agent knows precisely what it gets. It does not explicitly contrast itself with the siblings mark_read and post, but the 'call this first' framing implicitly positions it before them.

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 gives a clear trigger condition: call this first when starting a session, which establishes ordering versus the sibling write tools. It does not spell out when-not-to-use or name the alternatives directly, so it falls short of a 5.

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