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

Annotations already declare readOnlyHint and openWorldHint, but the description adds useful context beyond them: data is sourced live from the chain and refreshed every few minutes, and the ranking compares against a previous window. That freshness and provenance detail materially affects how an agent should present or trust results.

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 tight sentences: the core definition and metrics come first, followed by a short provenance/freshness note. Nothing is redundant or padded.

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 two-parameter, read-only ranked-list tool with no output schema, the description covers what is ranked, what metrics accompany each entry, and how fresh the data is. Minor gaps remain, such as tie-breaking or whether fewer than 'limit' results can be returned.

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%, so the baseline of 3 applies. The phrase 'change against the previous window' hints that the hours parameter defines both the measurement and comparison window, but the description adds no syntax or default detail beyond the schema.

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 a specific resource (Uniswap v4 hooks on Elysium) and a specific ranking criterion (most new pools right now), plus the metrics returned (change vs. previous window, share of new hooked pools). An agent can distinguish this from a plain enumeration tool like list_chain_hooks, 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?

Usage is only implied: 'gaining the most new pools right now' suggests this is the tool for trend/ranking questions rather than full inventories. There is no explicit statement of when to prefer it over list_chain_hooks or inspect_hook, and no exclusions or prerequisites.

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