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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, so the bar is lower, yet the description still adds real context: free and keyless, a 32768-byte input limit, no generated consensus, and no automatic paid fallback. It stops short of describing the output shape or failure behavior, but the cost and scope disclosures are genuine value beyond the annotations.

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 cost and purpose well, but 'No fetch' and 'no fetch, payment or automatic paid fallback' restate the no-fetch point, and the byte-limit sentence is tacked on after the alternative. Mostly tight, with noticeable redundancy across the two sentences.

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?

An output schema exists, so return values needn't be described, and the behavior/cost framing is solid. However, for a transformation tool with 4 params at 0% schema description coverage, the description leaves the parameters unexplained, which is a real gap for correct invocation.

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 0% and there are 4 parameters, so the description must carry the semantic load, but it never explains maxChars, maxComments, sourceUrl, or the thread structure. The mention of a 32768-byte input cap is the only limit-related detail, leaving the two size/limit parameters undocumented.

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 (Format) and resource (supplied Reddit comments JSON) and names the output precisely: a bounded post and reply tree with original Markdown, authors and direct links. The 'No fetch' clause implicitly separates it from fetch-based siblings like web_reddit_thread and web_thread_pack, so an agent can tell what it does without opening the 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?

Clear context: 'Supplied data only; no fetch, payment or automatic paid fallback' tells the agent to use this only when it already holds the JSON, versus fetching tools. It doesn't explicitly name an alternative sibling to use when fetching is required, so it stops short of a full when/when-not/alternatives statement.

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