list_subreddits

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

The description discloses side effects (read-only, no external HTTP calls) and determinism, which is critical for an agent. No annotations are provided, so the description fully compensates with clear behavioral traits.

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 description is three sentences, front-loaded with the primary purpose, followed by filtering and behavioral notes, then usage context. Every sentence adds value with no redundancy or fluff.

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?

Given no output schema, the description adequately explains return values (cooldown windows, flair vocabulary, last-posted metadata). It covers side effects, determinism, and parameter usage, making the tool's behavior fully understandable.

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?

The input schema has 100% coverage with a clear description for the profile_name parameter. The description adds only a paraphrased version ('allowed by that profile') but no additional constraints, formatting, or examples beyond the schema.

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 clearly states the tool returns all subreddits with metadata, using a specific verb 'Return'. It distinguishes from sibling tools (e.g., list_profiles returns profiles, not subreddits) and provides concrete use case context for composing reddit variants.

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?

The description gives explicit guidance: use list_subreddits to select a subreddit and obtain flair IDs before composing a reddit channel variant. However, it does not explicitly mention when not to use this tool or suggest alternatives, missing some depth.

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