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

No annotations exist, so the description carries the full behavioral burden. It discloses only billing per call, not whether the operation is read-only, what data shape is returned, what pagination semantics apply, or whether authentication/authorization is needed.

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 short and front-loaded, but it is under-specified rather than helpfully concise. 'Controversial Group: Explore.' adds almost no operational information, and the billing note does not make the description effective.

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 absent annotations, missing output schema, and 7 unexplained parameters, the description is far from complete. It does not explain the tool's return value, pagination behavior, or sorting semantics, leaving the agent to guess how to invoke it.

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 and 0% coverage, and the description adds no meaning to any of them. Param names like t, show, after, before, sr_detail, count, and limit are left unexplained, which is especially problematic since the description must compensate for the low schema coverage.

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?

Description says only 'Controversial Group: Explore.' This is too vague to state what resource is acted on, what verb is actually performed, or whether it returns posts/comments. It also does not differentiate it from sibling tools like get_subreddit_controversial or get_hot.

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 guidance is given for when to use this tool versus alternatives. The description provides no context about sorting scope, subreddit-specific usage, or when a sibling such as get_top or get_controversial would be more appropriate.

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