Get Subreddit Rules

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so restating 'read-only' adds nothing. 'Anonymous' does add a small piece of behavioral context — no authentication/credentials required — which is not covered by the annotations. Beyond that it says nothing about failure modes (e.g. nonexistent or private subreddit) or response behavior, so with the annotation bar already met this is a modest addition.

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?

Extremely tight: one clause stating the resource and its returned fields, then a two-word qualifier. Nothing is padded, and the resource scope is front-loaded. The trailing 'Read-only, anonymous' fragment is slightly clipped but still parses cleanly.

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 present, the description steps in to sketch the returned content, which is exactly the right compensation. For a single-parameter read tool with annotation coverage, nothing essential is missing; only the routing question versus sibling tools remains open.

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 description coverage is 100% and the single parameter is fully documented in the schema (name without the r/ prefix, with an example), so the schema carries the burden. The description adds no parameter-level detail, which is fine but yields the baseline 3.

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 names a specific resource (a subreddit's posting rules) and even sketches the shape of the result: short name, description, and applicable content kinds. That makes the tool's output distinguishable from generic subreddit metadata. It does not, however, differentiate itself from close siblings like get_subreddit_info or browse_subreddit, so it stops 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?

There is no explicit when-to-use statement and no mention of the alternative tools (e.g. get_subreddit_info) that an agent might confuse this with. Usage is only inferable from the name and one-line purpose. 'Read-only, anonymous' describes the call's nature, not the conditions under which it should be selected.

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