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

With no annotations, the description carries the full burden and does well: it discloses read-only status, a ten-minute marketplace cache, per-call pricing ($0.02), the scoring methodology, and a 'not financial advice' caveat. It stops short of failure modes (empty board, unknown chain behavior) or rate limits beyond the cache, so it isn't a 5.

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?

Front-loaded with purpose, then methodology, caching, and safety caveat in a compact block with no wasted sentences. The parenthetical weighting list is dense but earns its place by explaining the ranking. Minor tightening possible, but structure is strong.

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?

No output schema exists, so the description must cover returns—and it does precisely: 'each with floor, change, sales, score and a one-line reason.' Combined with read-only, caching, and cost disclosures, an agent has everything needed to call it correctly.

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 100% and both parameters have documented enums, so the schema does the heavy lifting. The description adds the 'for one chain' scoping and scoring weights but says nothing about the day parameter's today/yesterday limitation, leaving that entirely to the schema note. Baseline 3 is 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?

States a specific resource ('Today's flip board for one chain') with a concrete verb-like outcome: the ten NFT collections with the most momentum, ranked by a published score. The weighting breakdown (0.5 floor change, 0.3 sales pace, 0.2 listings thinning) makes the tool's output distinct from nft_floor and nft_pumps. However, it never explicitly names those siblings to route the agent, 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?

'Today's flip board' plus the schema note implies this tool is for current-day momentum only, and the caching note sets latency expectations. But no explicit when-to-use/when-not guidance or named alternatives (e.g., nft_pumps, nft_floor) appear in the description, leaving routing to inference.

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