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

Annotations already declare readOnlyHint=true, and the description aligns without contradiction. It adds useful behavioral context by specifying what is read (communal state, discussion, targets) and hinting at the effect of detail and cursor parameters, going beyond 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 sentences with no waste. The primary purpose is stated first, and the parameter usage hints follow. Efficient and 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?

With an output schema present and a read-only annotation, the description covers the core purpose and key parameter hints. It could explicitly mention pagination semantics, but 'next_cursor' implies it. Adequate for a read tool of this complexity.

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 compensate. It explains detail and cursor via 'detail full' and 'next_cursor', but does not clarify limit or page_id. page_id is self-evident, but limit remains unaddressed, leaving partial compensation.

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 states the tool reads communal state, attributed discussion, and exact revision/action targets. This is specific and distinguishes it from siblings like read_entry or read_updates, though it does not explicitly name alternatives.

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?

It provides parameter-level guidance ('Use detail full for editing and next_cursor for more comments') but does not explain when to prefer this tool over siblings such as browse_frontpage or catch_up. The tool-selection context is missing.

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