reddit get setup guide

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

Annotations already declare readOnly, idempotent, non-destructive and openWorld, so the safety profile is covered. The description adds substantive scope disclosure beyond that: it tells the agent this document carries prerequisites, unit conventions, renaming behavior and known limits — the exact things an agent would otherwise mis-plan around. Return shape is left to the output schema, which exists.

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?

Two sentences, no filler, with the content inventory first and the call-to-action second. Every clause carries information an agent needs.

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 an output schema present and no parameters, the description only needs to establish purpose and timing, which it does. The one remaining gap is not positioning this against the two other schema/guide-style siblings, which an agent choosing among three meta tools would want.

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?

Zero parameters, so there is nothing to disambiguate; baseline applies. Nothing in the description conflicts with the empty 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?

Names the resource precisely (setup guide for the Reddit connector) and enumerates its scope: coverage, prerequisites, units, renaming, known limits. That content list implicitly distinguishes it from every sibling, which are all data-fetching tools, though it never explicitly contrasts with reddit_get_write_schema or reddit_get_reporting_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?

"Read it before planning writes or answering what this server cannot do" gives a clear triggering condition tied to two concrete situations. It stops short of telling the agent when to prefer reddit_get_write_schema or reddit_get_reporting_schema instead, which are the closest alternatives.

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