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

With no annotations to clarify safety or side effects, the description carries the full burden but only mentions billing per call. It does not disclose read-only behavior, data scope, or any potential impacts, which is insufficient for a 7-parameter tool.

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 terse, but this is under-specification rather than effective conciseness. It front-loads no useful information and wastes the limited space on a vague tagline.

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 7 parameters, no output schema, no annotations, and a completely vague description, the tool is far from adequately documented. The description does not explain the tool's purpose, expected output, or parameter usage, making it nearly impossible for an agent to invoke correctly.

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 provides no explanation for any of the 7 parameters like 't', 'show', 'after', 'count', etc. All parameters remain cryptic, and the description fails to compensate for the lack of schema metadata.

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 'Hot Group: Explore' is vague and tautological, reiterating the name without specifying what 'hot' refers to or what actions are performed. It does not differentiate from siblings like get_top, get_rising, or get_controversial.

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 provided on when to use this tool versus alternatives. There is no mention of context, prerequisites, or exclusions, leaving the agent without decision-support.

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