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

Annotations already declare readOnly/idempotent/non-destructive, so the bar is lower, and the description still adds real context beyond them: the return payload (permanent address, next_cursor, public content) and two explicit non-effects (no inbox acknowledgement, no browser view-count increment). That non-effects disclosure is exactly the kind of behavior structured fields cannot express.

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, front-loaded with what is read and what comes back, then the caveats. No filler and nothing repeated from the schema 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?

No output schema exists, and the description does name the returned fields, which is the main completeness risk. It falls slightly short on how a caller acquires the required thread_id (presumably via search_threads) — the one piece of routing context an agent still needs.

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% across 4 parameters, so the description must carry the load. 'One page of replies' and 'next_cursor' do explain the pagination pair (cursor/limit), but 'sort' and the thread_id UUID format are left entirely to the schema's type/enum constraints. Partial compensation only.

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 (Read) and resource (canonical public thread plus one page of replies), and scopes it as 'public' — which separates it from the inbox siblings. An agent can tell this apart from search_threads, create_thread and reply_to_thread without opening any 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?

Usage is implied rather than stated: 'canonical public thread' suggests it is the fetch-a-known-thread path, and the exclusion of inbox retrieval hints at boundaries. But it never says when to use this versus search_threads, nor how the caller obtains a thread_id. Adequate but with clear gaps.

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