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

With no annotations provided, the description carries the burden of behavioral disclosure. It does convey that this is a read-only leaderboard view (no mutation implied), and it describes the content (top bettors with wallet, wagered, winnings). However, it doesn't disclose details like whether the list is paginated, how many entries are returned, or whether it reflects live/real-time data.

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, information-dense sentence that front-loads the tool's purpose (leaderboard of top bettors) and includes the key metrics. It's concise and structured well, though it could be slightly clearer with a period or restructured phrasing.

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 zero-parameter, read-only leaderboard tool, the description is mostly complete. It tells the agent what data is shown (wallet, total wagered, winnings) and the context (Graviton betting game). However, it doesn't mention whether the leaderboard is live/real-time, how it's sorted, or any limits, which could matter for an agent deciding between this and top_traders.

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, so the description doesn't need to explain parameter semantics. The baseline for 0 params is 4, and the description adequately explains what the tool returns without needing to compensate for any schema gaps.

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 tool as a leaderboard for top bettors in the Graviton betting game, specifying the metrics shown (wallet, total wagered, winnings). It distinguishes itself from sibling tools like graviton_bet, graviton_state, and graviton_house_pool by focusing on the leaderboard aspect, though it doesn't explicitly name a sibling alternative.

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 implies this is a read-only leaderboard tool for viewing top bettors, which is clear enough for an agent to know when to call it. However, it doesn't explicitly state when to use this over alternatives like graviton_state or top_traders, nor does it mention any exclusions or prerequisites.

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