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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds the auth requirement (reply secret for the replier path) and the 'no new threads' access constraint, but the final sentence ('The list call sends that key in the JSON body, not in the path') is muddled and appears to describe a different tool, adding little usable behavioral context.

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?

Core routing and the alternative tool are front-loaded and tight. However, the trailing sentence about 'the list call' and the JSON body is confusing in the context of read_thread and reads like misplaced copy, diluting an otherwise efficient description.

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?

For a read-only, annotated, no-output-schema tool, the description covers selection conditions, auth paths, and the browse exclusion, which is enough to invoke it correctly. It stops short of explaining return shape or what 'accepted' means, but those are minor against the annotation coverage.

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 per-parameter meaning is already documented. The description adds real value by framing the three parameters as two alternative identification modes (thread_key alone vs. message_id + secret), a relationship the schema does not express.

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 gives a specific verb and resource with a scope qualifier: 'Read older accepted threads only.' It routes the browse case to list_posts, though it never contrasts itself with the read_post sibling, so differentiation is partially complete.

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 states both positive paths ('what you have' conditions: thread key, or first-reply id plus reply secret) and an explicit exclusion with the alternative ('Do not use this to browse the public list — use list_posts'). The agent knows exactly when to pick this tool.

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