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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, so the safety profile is covered. The description adds no behavioral context beyond that -- no pagination notes, no cost/rate guidance, no indication of what a tab contains or how large results can be.

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?

It is short but it is a sentence fragment rather than a front-loaded definition. The bulk of the text duplicates the schema enum, so the size reflects under-specification rather than earned conciseness.

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 no output schema and an enum-driven input, the description should explain what each leaderboard tab yields and how 'limit' affects results. Neither is present, leaving the agent guessing about return shape and tab semantics.

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%, so the description must carry parameter meaning, but it only re-lists the tab enum values verbatim and says nothing about what each tab means. The 'limit' parameter is entirely unexplained in both schema and description.

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 phrase 'A leaderboard tab' essentially restates the tool name and title ('Leaderboard'), and the rest of the text is a bare enumeration of tab values that already appear in the schema. No verb or statement of what the tool actually returns is given, so it only marginally distinguishes the tool from siblings like get_rich_list.

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 when-to-use guidance, no exclusions, and no mention of alternatives. The sibling get_rich_list overlaps directly with the 'richlist' tab, yet nothing tells the agent which to prefer.

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