Capture Reddit thread

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

Adds real context beyond the annotations: no API credentials or page-allowlist needed, output saved with source_type reddit_thread, failures return an error, and recapturing can replace an existing corpus and metadata (consistent with destructiveHint=true, notReadOnly, non-idempotent). It stops short of mentioning rate limits, pagination, or how large a thread can be captured.

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?

Four sentences, purpose and scope front-loaded, followed by alternatives, then auth/return/error behavior, then the mutation caveat. No sentence restates the title or 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?

There is no output schema, and the description compensates by naming the return payload (captured content, comment counts, saved item ID) and the failure mode. Combined with the disclosed replacement semantics and credential/allowlist behavior, an agent has everything needed to call and interpret it.

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 100%, so depth_limit and score_threshold are already fully documented with defaults and bounds. The phrase "filtered comment tree" hints that filtering occurs but adds no format or behavioral detail beyond the schema, so the baseline 3 applies.

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 — capturing a Reddit post plus its filtered comment tree into a local discussion corpus — and immediately contrasts itself with uoink_page and uoink_url. An agent can distinguish this from the general capture siblings 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?

"Use when replies matter" gives the positive selection condition, and the same sentence names the two alternatives (uoink_page for prose, uoink_url for video) with the condition that picks each. Both when-to-use and when-not-to-use are explicit.

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