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

No annotations are supplied, so the description carries the full behavioral burden. It does add useful context beyond structure: the metrics surfaced (counts, hype, rank change) and the cost signal '[Free · 1 credit]', which is genuinely behavioral. However, it never explains what 'rising' or 'hype' are computed from, whether results are paginated/ordered, or what the history mode returns.

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 plus a bracketed cost tag — no filler. It is slightly over-compressed: 'hype' and the 7d/30d phrasing cost clarity even as they save words.

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?

One wrong thing worth flagging: with no annotations and no output schema, this description has to do the work itself, and it partly does by listing the returned metrics. The missing pieces are ordering, pagination, and what the history mode yields, which for a 5-parameter read tool is a real gap. Score of 3 would be more defensible than 5.

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 only 20% (just key is documented), so the description should compensate more than it does. It adds the entity-type vocabulary and frames the time dimension as '7d/30d,' but that framing doesn't cleanly map onto the days range (7–90) and window enum (week/month), leaving days, limit, and window without added meaning beyond their enum bounds.

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 and the metrics returned (rising topics/datasets/authors/affiliations with 7d/30d counts, hype, rank change) and explicitly covers a second mode, 'the history of one entity.' An agent can tell what it produces, though it isn't differentiated by name from plausible siblings like library_emergent_topics or dataset_leaderboard.

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?

The dual mode (ranking vs. single-entity history) is implied by the description and reinforced by the key parameter, but there is no explicit when-to-use guidance and no named alternative for the ranking case. The agent must infer which sibling to prefer for emergent topics or leaderboards.

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