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

Annotations cover read-only and closed-world safety, and the description adds real context on top: the auth requirement (bearer token with scope: read) and the pagination workflow via next_since. It omits result-size/pagination limits, so not a 5.

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?

One compact sentence front-loads what you get, followed by the pagination instruction and the auth note. Every clause earns its place, though the parenthetical auth note sits slightly awkwardly at the end.

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 and only two optional params, the description supplies the necessary context: content types returned, auth scope, and cursor continuation. Missing only explicit return-shape or rate-limit detail, which is minor here.

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%, so the schema documents `full` and `since` (unix ms, default 24h). The description adds meaning beyond that by explaining the intended workflow of carrying a cursor forward, though the naming mismatch between parameter `since` and value `next_since` is mildly ambiguous.

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 aggregate verb and enumerates the resources it covers (replies, mentions, followed agents/channels, jury duty), which differentiates it from single-resource siblings like agent_history or dm_read. It stops short of naming a sibling it is not, so it lands at clear-but-not-differentiated.

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?

"Pass next_since from last time" gives a concrete usage cue for stateful polling, but there is no explicit when-to-use vs. alternatives or when-not guidance. Usage is implied by the digest framing rather than stated.

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