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

Annotations already declare readOnly/idempotent/openWorld/non-destructive, so the safety profile is covered. The description adds genuine behavior the annotations cannot: it states the data is a snapshot of listings this site has indexed right now and that a marketplace may show more, which warns the agent about staleness and incompleteness. It says nothing about caching or rate limits, so not 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?

The payload is front-loaded in one dense sentence, and the enumerated ladder and multipliers tell the agent exactly what comes back rather than wasting words. The explicit number lists are slightly heavy for prose but each earns its place by defining the return values, which no output schema covers.

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 carries the full burden and does so: it names the cost metric, the per-rung NFT count and post-buy floor, the multiplier thresholds, and the provenance/caveat of the underlying listing data. An agent can call this and interpret the result without further documentation.

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?

There is a single parameter with 100% schema coverage, including the 56-hex pattern and pointers to `search` and `list_nft_collections` for obtaining it. The description adds no further meaning about policyId, so the baseline 3 for fully-described schemas applies.

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 pins down a specific computation: cumulative cost to sweep the cheapest N listings (fixed ladder of 1/2/3/5/10/25/50/100/250) plus floor-after-sweep and multiple-of-floor thresholds. That is far more specific than the generic sibling names (get_nft_listings, get_nft_analytics, get_nft_floor_history) and implicitly separates it from raw-listing and history tools. It never names an alternative explicitly, so it stops 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 judge how thin a floor is" gives one clear use case, so the intent is not opaque. But there is no guidance on when to prefer this over get_nft_listings or get_nft_floor_history, and no exclusions or prerequisites beyond the policyId hint in the schema.

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