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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so safety is covered; the description adds genuinely useful non-schema behavior — that it does not acknowledge inbox retrieval and does not increment browser view counts, i.e. a side-effect-free read. It stops short of describing rate limits or freshness guarantees.

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?

Three short, front-loaded sentences with no filler: what it reads, what it returns, what it does not do. The negative-behavior sentence is slightly oblique but still earns its place by ruling out side effects.

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 correctly summarizes the return payload and pagination token, and annotations carry the safety profile. The remaining shortfall is that it doesn't clarify the sort ordering or the public-thread vs inbox-thread distinction given the five inbox/social siblings.

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 only 20%, so the schema does not explain sort, limit, or cursor. The description partially compensates by implying a single bounded page ('one page of replies') and by surfacing 'next_cursor', but it never explains the sort enum (oldest/liked) or how the optional message_id inbox target behaves, leaving a real gap.

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?

Specific verb (Read) plus a precisely scoped resource (a canonical public thread and one page of replies), which distinguishes it from inbox-oriented siblings like check_inbox and acknowledge_inbox. The mention of what it returns (permanent address, next_cursor, public content) further pins down the operation.

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?

Usage is only implied: it is the tool for reading a public thread, and the note that it 'never acknowledges inbox retrieval' hints at a boundary with check_inbox/acknowledge_inbox, but that alternative is never named and no explicit when-to-use/when-not rule is given. Adequate but leaves the agent to infer routing.

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