reddit_global_pool

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

With no annotations provided, the description takes on the full burden and explicitly states 'no DB writes', which is a key behavioral trait. It also characterizes the operation as informational. It does not address rate limits or auth, but for a simple read-only stats tool, this is adequate.

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 two concise sentences with the main verb and resource front-loaded. There is no fluff; every phrase 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?

The tool is simple, but the description leaves the return structure ambiguous ('stats' vs 'count') and does not explain the role of brandId in a 'global' dataset. Since there is no output schema, a bit more detail would improve completeness.

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 provides a full description for brandId ('Brand ID (defaults to active brand)'), so schema coverage is 100%. The tool description does not add meaning about how brandId affects the 'global' stats, so it stays at the baseline without exceeding it.

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 action ('Return'), the resource ('global subreddit dataset'), and the specific metric ('count of known subreddits available for matching'). It distinguishes itself from sibling reddit tools by emphasizing 'global', which differentiates it from brand-specific pool tools like reddit_get_pool.

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 implies usage via 'Informational only — no DB writes', suggesting it is safe for read-only queries. However, it does not explicitly mention alternatives or when not to use it, so the guidance is implied rather than explicit.

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