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

No annotations are provided, so the description carries the burden of behavioral transparency. It discloses the HTTP method (GET), the endpoint URL, the real settlement detail, and a graceful failure message ('returns "rails not yet live" gracefully if upstream is not yet deployed'). It does not mention response format or side effects, but the operation is a safe read and the graceful error adds 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 three sentences, each earning its place: purpose, endpoint/URL, and graceful failure behavior. It is concise, front-loaded with the main purpose, and contains no fluff.

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 simple tool with one optional parameter and no output schema, the description covers the essential usage including the endpoint and error handling. However, it does not describe the return structure (e.g., fields like agent addresses and amounts), which would be helpful for the agent to know what to expect. Still, it is nearly complete for the tool's simplicity.

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 coverage is 100% with a clear enum and default, so the baseline is 3. The description adds value by showing the URL template with ?window=<window>, connecting the parameter to the actual request. This goes beyond the schema's basic documentation of the enum values.

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 states the tool's purpose: 'Top earning agents on the Hive Civilization, by attribution payout in USDC.' This uses a specific verb ('list' implied) and a distinct resource (leaderboard), and it is distinguishable from siblings like hive_earn_me (individual earnings) and hive_earn_register (registration).

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 clearly implies when to use the tool (to view top earners) and the context is obvious. However, it does not explicitly mention alternatives or when not to use it, unlike a perfect score. Sibling tool names provide differentiation, but the description itself does not reference them.

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