Reddit subreddit listing

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

Annotations already declare read-only, open-world, non-idempotent, and non-destructive. The description goes well beyond them: auth via environment variables named by telos.reach.doctor, pacing from Reddit's rate-limit headers, per-host pacing with backoff on 429 and 503, no login/cookies, and a receipt return. This is rich, precise behavioral disclosure.

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 dense sentences, front-loaded with usage and safety, then network behavior, then return format. Every clause adds a distinct fact (auth source, pacing, backoff, no login/cookies) without filler.

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 states the return format ('JSON posts and a receipt'). Combined with annotations, it covers auth, rate limiting, backoff, and network profile sufficiently for an agent to invoke correctly. It omits parameter defaults/behavior, but the schema partly covers that.

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 50%, with enums for sort/time and min/max on limit, but the description adds no parameter-level meaning—no explanation of sort/time behavior, limit defaults, or interaction between parameters. It only implies 'posts' and 'subreddit' generally, failing to compensate for the coverage gap.

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: 'needs posts from a subreddit' via Reddit's official Data API. Clear what the tool does, but it does not explicitly differentiate itself from the sibling tool telos.reddit.comments, which likely handles comments versus posts.

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?

Opens with 'Use when an agent needs posts from a subreddit...' giving a clear context for invocation. It does not state when not to use it or name alternatives such as telos.reddit.comments, so it lacks exclusions but provides clear positive guidance.

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