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

readOnlyHint=true already declares the safety profile, so the description is free to add behavioral detail, and it does: pagination is cursor-based forward paging, results come back oldest first, and the cursor is a post seq. It does not discuss volume, rate limits, or what a post record contains, but the ordering and paging semantics are genuinely useful additions.

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?

Two sentences, no filler, with the operation and ordering front-loaded and the usage caveat held to the end. Every clause carries 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?

With no output schema, the description still conveys the shape of the call: scoped to a problem or the whole lab, paged forward from a seq, oldest first. It does not hint at what a returned post looks like beyond being part of a "history", which is a minor gap for a read tool with a well-covered schema.

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 75%, so the schema already documents `slug`, `cursor`, and `problem`. The description adds only a slight gloss on `cursor` ("a post seq", "after `cursor`") and confirms the omit-problem-for-whole-lab scope, largely restating what the schema says. The baseline of 3 for high coverage is appropriate.

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+resource (pages through a problem's history / the whole lab's posts) plus ordering (oldest first) and cursor position. An agent can distinguish it from `post` (write) and `list_problems` (problem metadata). It stops short of naming a sibling directly, so it lands at 4 rather than 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?

"Use only if the context pack is not enough" gives an explicit gating condition for when to reach for this tool versus relying on already-provided context. The guidance is real but relies on the reader knowing what a "context pack" is and mentions no named alternative tool, so it is clear context rather than a full when/when-not/alternative statement.

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