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

Annotations only declare safety hints (read-only, idempotent, non-destructive); the description adds substantive behavior they cannot: the exact ordering of results, the truncation caveat at X's "Show more" fold, the 404 condition, and per-post billing with a concrete credit formula. These are the operational facts an agent needs before calling and no structured field carries them.

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?

Front-loads the purpose, then stacks return shape, argument rule, exclusion, truncation limit, error case, and cost in short declarative sentences. Every sentence contributes a distinct fact; nothing is restated from the title or annotations.

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 correctly carries the burden of describing return content and ordering, and it also covers the failure mode and pricing. For a single-parameter read tool, nothing an agent needs in order to call it correctly or interpret results is missing.

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 the baseline would be 3, but the description adds real meaning the schema lacks: the id may be any post in the thread, not just the head, which changes how an agent sources the argument. That is a semantic clarification beyond the schema's "post id or status URL" note.

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 and resource ("Get the author's thread containing a post") and immediately defines the returned set: earlier posts it continues from, the post, and continuation below. It explicitly separates itself from replies by pointing to the replies tool, so an agent can distinguish it from siblings like get_x_post or get_x_replies without opening a schema.

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?

Gives an explicit invocation rule ("Pass any post in the thread") so the agent knows it need not hunt for the root, and names the exclusion plus the alternative tool for other people's replies. That is a genuine when-to-use / when-not-to-use / alternative routing statement, the top of the scale.

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