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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered; the description adds real value beyond them by disclosing latency ('a full scan can take a few minutes') and framing the output as evidence-based risk ranking rather than a prediction. Paid-tier behavior (x402) is left entirely to the schema.

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 scope, then the methodology and the latency caveat. No filler; each sentence carries distinct 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?

With no output schema, the description should hint at the shape of a result (a ranked list with scores and summaries), which it only gestures at via 'ranked by evidence-based risk analysis'. Paid-tier and limit semantics also remain unaddressed, so an agent cannot fully predict the response.

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 50%: tier and period carry descriptions, chain and limit do not. The description restores some meaning for chain ('Ethereum and Base') and period, but says nothing about how limit interacts with ranking (e.g., that it returns the top-N ranked results), leaving one parameter undocumented in both places.

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 concrete verb and resource: new NFT collections launched on Ethereum/Base within a stated window, sourced from onchain contract deployments and risk-ranked. This is clearly distinct from analyze_nft_collection (discovery of new launches vs. analysis of one known collection), though the sibling is not 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 implied by the 'new launches' framing, and 'Not a profit prediction' usefully sets expectations against misuse as a trading signal. However, it never states when to prefer this over analyze_nft_collection, nor any prerequisite or exclusion conditions.

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