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

Annotations already declare readOnly/idempotent/non-destructive, so the description earns credit for adding semantic context the annotations can't: it defines what "volume" means (indexed USDC transfers, explicitly not PnL or AUM) and states the limit bounds. That metric definition is essential for interpreting results and is not recoverable from structured fields.

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?

Three short sentences, front-loaded with the resource and ranking basis, then the disambiguation of "volume," then the parameter bound. Nothing is redundant and every sentence carries information.

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?

An output schema exists, so return shape needn't be described; the description covers scope (Base), metric semantics, and parameter bounds. For a single-parameter read-only ranking tool, nothing an agent needs to call it correctly is missing.

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 0%, so the description must compensate. It does, by stating "Limit 1-20" — giving both the valid range and the notion of a bounded page size that the bare integer schema omits. It doesn't restate the default of 5, but the range is the missing key detail.

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?

States a specific resource (on-chain AI agents on Base) and an explicit ranking basis (indexed USDC transfer volume and transaction count), which lets an agent distinguish it from sibling rankings like get_bazaar_organic_ranking or get_top_smart_buyers. No sibling is named directly, so it falls short of a 5.

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?

"Use it to discover which agents actually move money" gives a positive usage cue, but there is no when-not guidance and no named alternative for adjacent needs (e.g., trust checks or Solana agent discovery). Usage is implied rather than fully routed.

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