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

readOnlyHint already declares the safety profile, so the bar is lower; the description adds real context by disclosing pagination behavior ('next_cursor for more comments') and that detail=full is the mode for editing. It does not contradict the annotation.

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 dense sentences, front-loaded with the read operation before the routing guidance. Every clause maps to a distinct decision (which detail mode, which pagination, which sibling), though the first sentence is compressed to the point of being cryptic.

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?

An output schema exists so return values need not be restated, and annotations cover safety; the description supplies the routing and mode-selection guidance an agent needs. It is nearly complete, missing only limit/page_id clarification.

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 0%, so the description must carry all four parameters. It partially compensates by naming the 'detail full' mode and the next_cursor pagination mechanism, but leaves limit and page_id semantics unaddressed, so it only covers half the surface.

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 the verb 'Read' and describes what is retrieved (communal state, attributed discussion, revision/action targets), distinguishing it from read_page_history and read_page_revision by name. The phrasing is somewhat abstract about what a 'page' actually is, but the operation and its scope are inferable.

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 routes the agent: 'Use read_page_history for earlier edits or read_page_revision for a revision ID from catch-up,' and ties detail/cursor to editing and comment pagination. It provides clear when-to-use context for alternatives, though it never states when NOT to use this tool.

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