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

With no annotations provided, the description carries full responsibility for behavioral disclosure. It only mentions billing cost, not side effects, rate limits, required permissions, or output format. This is entirely insufficient for a tool that likely makes API calls.

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 extremely short, but it is not appropriately concise—it omits essential functional information. The two sentences (category label and billing) are not structured to help the agent understand the tool; the billing note is tangential and the category label is redundant with the tool name.

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 the tool's complexity (7 optional parameters, no output schema, no annotations), the description is grossly incomplete. It does not explain what the tool does, how to use it, or what results to expect, making it virtually unusable for an AI agent.

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 schema has 7 parameters with 0% description coverage, and the tool description mentions none of them. It fails to explain the meaning of parameters like 'show', 'after', 'limit', or 'subreddit', leaving the agent without any guidance on how to construct valid inputs.

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 category label ('Subreddit Posts > New Group: Subreddit Posts') rather than a clear statement of what the tool does. It implies fetching new subreddit posts but fails to explicitly state an action or resource, making it nearly a tautology of the tool name.

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 guidance on when to use this tool versus its many siblings (e.g., get_hot, get_top, get_controversial). No context, prerequisites, or alternative recommendations are provided, leaving the agent to guess.

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