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

No annotations exist, so the description must carry the behavioral burden, and it does add real value: it discloses result ordering (listings cheapest first, offers highest first) and the freshness contract ('every order is re-checked on-chain; stale ones are skipped'). It stops short of stating read-only nature explicitly, pagination/result limits, or failure behavior.

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 sentences, no filler, with the data categories and their orderings front-loaded and the freshness caveat placed last where it belongs. Every clause 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?

With no output schema and no annotations, the description does the heavy lifting: it enumerates the three data categories, their sort orders, the traits inclusion, and the on-chain validation behavior. Missing detail on response shape/pagination limits the score to 4.

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 0% and the single parameter 'id' has no description, but the description compensates by defining it as the punk id, noting it also yields that punk's traits, and specifying the omitted-id behavior (whole collection). Baseline for one param is 4; this meets it despite the undocumented minimum/format.

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/resource: returns live listings, offers (including collection offers), and recent sales for a given punk id or the whole collection. The scope is clear enough to separate it from get_token (token metadata) and get_status, though it never names a sibling 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?

It implies the usage mode by saying data is returned 'for punk #id ... or the whole collection', which tells the agent the id is optional and omitting it means collection-wide. There is no explicit when-to-use vs get_token/get_status guidance and no note about how often to call it.

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