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

Annotations already establish readOnly/idempotent/non-destructive and a closed (non-open-world) data source, so the safety profile is covered. The description adds genuinely useful behavior beyond that: the free tier is capped at 10 entries and masks addresses, which tells the agent the output differs by credential tier. It does not explain what changes with a Pro key, so it is not fully transparent.

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?

Two sentences, no filler, with the core ranking definition front-loaded before the tier caveat. The first sentence is a dense comparative construction that takes a moment to parse, but nothing is wasted and it fits an easy-to-scan size.

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 read-only, zero-required-parameter tool the description is close to adequate, and with no output schema the description carries the burden of explaining returns — it gives the ranking basis but not the fields or the fact that masked results are still ranked. Combined with the unstated meaning of windowDays and chain, it is the minimum viable rather than complete.

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 only 33% — only 'limit' carries a description, and chain/windowDays are documented solely by enum values. The description mentions the top-10 default (relevant to 'limit') but says nothing about the chain filter or what a 30 vs 90 day window means, 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?

The description names the resource (wallets) and the ranking metric precisely: realized LP performance of closed positions versus a hold benchmark. That is far more informative than the bare title 'Smart-LP leaderboard' and easily distinguishes it from siblings like list_signals or signal_track_record. It stops short of stating that the output is a ranked list with a defined shape, but the intent is unambiguous.

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 when-to-use guidance, no mention of alternatives, and no statement of prerequisites such as needing a Pro key. The 'Without a Pro key' clause is a result-tier caveat rather than invocation guidance, so an agent still cannot tell when this tool is the right choice over the other analytics siblings.

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