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

Annotations already establish readOnlyHint=true and openWorldHint=false, but the description adds real methodology: profit is realized and net of fees, and probable market makers are filtered out. That materially changes how an agent should interpret the ranking. It stops short of noting any pagination or result-size behavior.

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 dense, front-loaded sentence that packs definition, ranking basis, exclusion rule, and returned fields with no filler. The trailing field list is slightly list-like but earns its place since there is no output schema.

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 2-parameter read-only tool with no output schema, enumerating the returned metrics is a genuine fill-in. The gap is the undocumented 'limit' parameter and the 25-row cap, which an agent needs to call correctly.

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?

Only 'window' has schema documentation ('Days to count (default 30)'); 'limit' has no description in the schema and none in the description. At 50% coverage the description should compensate, but it says nothing about the limit cap of 25 or the window enum's effect on the leaderboard.

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?

Names the resource (NFT flipper leaderboard), the ranking basis (realized profit after fees), and the exclusion rule (likely market makers). It also enumerates the metrics returned, so it is distinguishable from siblings like 'wallet' or 'collection', though it is phrased as a noun label rather than a verb+resource action.

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 indication of when to pick this over siblings such as 'wallet' or 'collection', nor any prerequisites. 'Likely market makers left out' is a data-scope statement, not usage guidance.

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