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

There are no annotations, so the description must fully disclose behavior, but it only contains a group label and billing note. It does not mention read-only semantics, authentication, pagination, or any caveats.

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 text is short, but it is under-specified rather than concisely informative. 'Billing per call: 1 Credits' is operational metadata, and 'Group: Subreddit Posts' is a redundant structure label. No sentence helps the agent select or invoke the tool correctly.

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?

This tool has 8 parameters, no required fields, no annotations, and no output schema, yet the description gives no context about ordering, default values, pagination behavior, or return payload. The agent would have no basis to understand what the endpoint returns or how to configure the request.

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 0% and the description describes none of the 8 parameters. The schema only lists parameter names and a few examples, with no meaning for g, show, after, before, or sr_detail. The description adds no compensatory clarification.

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 is essentially a restatement of the title: 'Subreddit Posts > Hot Group: Subreddit Posts.' There is no verb or explicit statement like 'retrieves hot subreddit posts,' so the tool name carries the entire meaning. It weakly distinguishes from siblings via 'Hot,' but does not explain what the tool actually does.

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?

No usage guidance is provided: no 'when to use,' no comparison to alternatives like get_subreddit_new or get_subreddit_top, and no mention of required context. The description gives no direction on selecting this over its many siblings.

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