Reddit post and comments

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

Beyond the annotations (readOnlyHint, openWorldHint, destructiveHint=false), the description discloses auth source (user's Reddit app credentials in env vars named by telos.reach.doctor), network egress with a single honest User-Agent, per-host pacing with backoff on 429/503, and no login or cookies. This is exactly the operational context an agent needs before invoking a network tool.

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?

The trigger condition is front-loaded in the first clause, and the remaining sentences each carry distinct operational payload (auth, network policy, return shape). It is dense and slightly run-on but nearly every clause earns its place.

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 must cover returns and it does ('Returns JSON comments with depth and a receipt'), while also covering auth, network behavior, rate-limit handling, and the read-only profile. Nothing an agent needs to call it correctly 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 schema already documents post_id (with/without t3_), depth, and limit. The description adds only that returned comments carry depth, not any semantics for limit or depth beyond the schema—baseline 3 is appropriate.

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 states a specific verb and resource: retrieve one Reddit post plus its comment tree via the official Data API. The 'one post' scope implicitly separates it from the sibling telos.reddit.listing, but it never names that sibling or draws the contrast explicitly, so it falls short of a 5.

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 an agent needs one Reddit post and its comment tree' gives a clear trigger condition. It offers no when-not guidance or explicit alternative (e.g. telos.reddit.listing for feeds), so it is clear context without exclusions.

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