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

The annotations already declare readOnlyHint: true, idempotentHint: true, and destructiveHint: false, establishing a safe read operation. The description adds minimal incremental behavioral context (the SmartScore scoping) but doesn't disclose return semantics or the meaning of 'elite'; the annotations carry the transparency load.

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 a single 16-word sentence that immediately tells the agent when to fire, with zero filler or restatement of the tool name. Every word earns its place.

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?

For a 0-parameter, read-only lookup with a provided output schema, the description covers the essentials. It could arguably have clarified what qualifies as 'elite,' but the low complexity and strong annotations make the description sufficient.

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 tool has zero parameters and trivially 100% schema description coverage, so there is nothing for the description to clarify. Per the rubric, zero-parameter tools receive a baseline of 4, and the description makes no errors or omissions.

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 clearly identifies the purpose with a specific resource ('elite leaderboard by SmartScore across exchanges') and references the get action. It effectively differentiates from sibling tools like get_top_traders and get_signals by naming the exact data domain and filter.

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 phrase 'Use this when the user specifically asks' provides clear usage context and implies the tool should not be used for other leaderboard types ('by SmartScore'). However, it stops short of explicitly naming alternatives or exclusions—e.g., it could have noted 'for other rankings, use get_top_traders'—which keeps this at a 3.

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