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

The annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description adds two useful facts not in the annotations: the data is public (no auth needed) and the returned rows are server-ranked rather than caller-sorted.

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?

One tightly written sentence that front-loads the action and appends the endpoint and return semantics. No padding, though it is arguably too short for six undocumented parameters.

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, no enum hints, and six parameters at zero schema coverage, the description does the minimum: it names the ranking dimensions but not their accepted values. An agent still cannot call this reliably without trial and error.

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% across 6 parameters, so the description carries the full burden. It names four of them (board, period, role, metric) but gives no valid values, formats, or meanings, and omits 'q' and 'limit' entirely, leaving the agent unable to populate any field confidently.

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?

States a specific verb and resource ('read the public Earn leaderboards') and even cites the backing endpoint, so the agent knows exactly what the tool retrieves. It does not distinguish itself from the sibling memeswap_earn_summary, which is the main remaining ambiguity.

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?

'Use to read...' implies the read/query context, but there is no guidance on when this leaderboard tool is preferable to memeswap_earn_summary or which board/period combinations are meaningful. Usage is implied rather than stated.

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