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

Annotations already cover read-only and closed-world, so the description correctly focuses on behavior: the 50-per-page pagination, that 7d fields are true rolling sums including the latest day, that 24h changes are null when the prior day has no value, and the upstream free data source. The null-handling note is the kind of gotcha an agent could not get from annotations.

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?

It leads with the core identity and page size, then adds caveats, with no filler sentences. The long opening clause is dense and could be split, which keeps it from a 5.

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?

There is no output schema, so the description must convey the return shape, and it does name the key returned concepts: 24h change, chains, version splits, and the 7d fields. Field names and types are not enumerated, but for a three-parameter read tool this is close to sufficient.

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 100% and both sort parameters have enums with defaults, so the schema already establishes the full parameter contract. The description only restates the page size that is already in the schema and adds no sorting guidance beyond it, making the baseline 3 appropriate.

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 states a concrete verb and resource (protocols ranked by fees or revenue) plus the ranking window, so the agent knows exactly what this returns. It stops short of naming a sibling such as rank_projects or project_metrics, so differentiation is inferred rather than stated.

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?

Usage is only implied: the description says the data is the latest completed day, which tells the agent this is not a historical or range-query tool, but there is no explicit when-to-use or when-not-to-use guidance and no mention of the alternative ranking tools in the sibling list.

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