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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds the non-obvious aggregation behavior (wallets folded into one collector profile), which materially affects how results should be read. However, it never states what the ranking is based on or how pagination behaves, which are the key behavioral unknowns for a ranking tool.

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?

A single tight sentence with the resource and the grouping behavior front-loaded and no filler. It is arguably too terse, but nothing written is wasted.

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 and three parameters, the description should cover ordering criterion, page window behavior, and result shape — none of which appear. An agent knows roughly what the tool is for but not how to page it or interpret the ranking.

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 33%: only 'collection' is documented (name, slug, or project ID). The description says nothing about 'limit' or 'offset' despite their being page controls for a ranked list capped at 500, so it does not compensate for the coverage gap.

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: "Rank who holds a BrainDrops collection." The addition of wallet grouping identifies the aggregation level, which distinguishes it from the per-wallet get_wallet tool, though no sibling is named explicitly.

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 choose this over get_collector, get_wallet, or list_collectors, and no note on prerequisites or typical use (e.g., leaderboard views vs. ownership lookup). Usage must be inferred entirely from the title and the word "Rank."

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