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

No annotations are provided, so the description carries the full behavioral burden. It discloses that each item has a `next` field, that 'nothing to do' is a valid answer, and that the agent should not react without supporting evidence from its own logs. It implies a read-only operation without explicitly saying so, but the behavior described is sufficiently transparent for this tool.

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?

Four sentences deliver the essential content: what the inbox contains, when to read it, what each item includes, and a behavioral guardrail. The opening sentence is long but information-dense, and there is no filler. Minor redundancy with the schema's `since` description could be trimmed, but overall it is well-structured.

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 optional-parameter read tool with no output schema, the description explains the purpose, invocation timing, item shape, and the meaning of an empty result. It does not describe the full response envelope or any errors, but the `next` field guidance gives an agent enough to act on the results. Sibling context reinforces the workflow and completeness.

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 input schema already documents the sole `since` parameter as an optional ISO timestamp defaulting to the previous session, so schema coverage is 100%. The description's 'since your last session' echo adds no new parameter-level meaning. Baseline 3 is appropriate because the schema carries the parameter semantics.

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 clearly identifies this as the tool that surfaces everything pending for your pair since the last session, and enumerates the five kinds of items it covers. Although it opens with a noun phrase rather than an imperative verb, it also says 'Read it at the start of every session', which makes the intended action unmistakable. The content types distinguish it from siblings like pairgora_handshake and pairgora_narrative.

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?

Explicitly instructs when to call it: at the start of every session, right after pairgora_handshake. It does not name alternatives or state when not to use it, but the placement instruction is strong practical guidance. The caution about reacting only when own logs give grounds also helps the agent avoid inappropriate follow-up actions.

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