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

With no annotations, the description carries the full burden of disclosing behavior. It fails to mention what the tool returns, whether it has side effects, or any operational constraints. 'Billing per call: 1 Credits' is a cost note, not behavioral transparency.

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, but this is under-specification, not conciseness. It contains no substantive information and does not earn its place. A single vague phrase does not constitute a useful tool description.

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 six parameters, no output schema, no annotations, and a meaningless description, the tool is entirely underspecified. The agent cannot infer the tool's purpose, input requirements, or return value, making it unusable in practice.

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 adds no parameter information. All six parameters are undocumented in both the schema and the description, leaving the agent completely in the dark about what 'show', 'after', 'count', 'limit', 'before', and 'sr_detail' mean.

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 'Best Group: Explore' provides no clear verb or resource. It does not state what the tool does, and 'Explore' is too vague to distinguish it from sibling tools like get_hot or get_top. It reads more like a heading than a functional description.

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?

The description gives no indication of when to use this tool versus alternatives. There is no mention of scenarios, prerequisites, or exclusions. The agent has no guidance on choosing get_best over similar listing tools.

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