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

With no annotations provided, the description carries the full behavioral burden and discloses nothing: no ordering/ranking semantics implied by 'leaderboard', no indication of whether it requires region, no pagination or default-season behavior, no auth notes. This is a bare label, not behavioral context.

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 certainly short, but it is under-specified rather than concise; a two-word fragment gives no front-loaded verb or scope. Brevity here reflects missing content, not efficiency.

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 annotations and no output schema, the description is the only source of behavioral context and it provides none. For a three-parameter ranking query with a required region and a season default, an agent needs far more than 'Onslaught leaderboard' to call it 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 100% – limit, region, and season are all documented in the schema itself, including enum values and the default-current-season note. The description adds nothing beyond the schema, which is the baseline-3 case.

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 'Onslaught leaderboard' is essentially a restatement of the tool name (players_onslaught) with the single added word 'leaderboard'. It does not state what data is returned or how it differs from the sibling players_onslaught_history or players_by_nickname_onslaught, leaving an agent unable to distinguish them.

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 alternatives. The nearby siblings players_onslaught_history and players_by_nickname_onslaught are plausible substitutes, but the description neither names them nor gives any use condition.

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