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

Annotations already declare readOnlyHint, idempotentHint and non-destructive, so safety is covered. The description adds real behavioral detail beyond that: reply ordering is oldest-first, pages are capped at 30 replies and a 16,000-character budget, and has_more signals further pages. That is substantive disclosure of pagination and truncation behavior.

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 sentences with no filler, front-loaded with the purpose and followed by pagination constraints. It is efficient, though the trailing cursor sentence is slightly muddled by the name mismatch with the schema.

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 must carry return-value context, and it does explain reply ordering, page size, the character budget and the has_more flag. It still does not describe what "full thread context" actually returns (participants, metadata, etc.), which is a modest gap for a read tool.

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% with both parameters documented, so the baseline is 3. The description adds paging semantics but refers to "next_reply_cursor," a name that does not match the input parameter "reply_cursor," which could mislead an agent about which field to pass on the next call.

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 states a specific verb and resource ("Read full thread context and replies") and clarifies the scope as a full thread rather than a single message. It implicitly distinguishes itself from write siblings like relay_reply and relay_post, but never names an alternative tool, so the differentiation from relay_catch_up in particular is left to inference.

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 gives pagination guidance ("Use next_reply_cursor when has_more is true"), which is genuinely actionable, but it provides no when-to-use versus when-not-to-use guidance relative to siblings like relay_catch_up or relay_read equivalents. Usage is implied rather than stated.

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