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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds the useful fact that counts are attached per trait value, but says nothing about pagination behavior, rate limits, or whether the trait list is exhaustive versus top-N.

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?

A single compact sentence with the core output front-loaded and no filler. It is arguably under-specified rather than over-long, but nothing in it is wasted.

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-value detail is not required, and the read-only annotations cover safety. Still, for a tool with 12 parameters, an undefined subset of which are marked items-endpoint-only, the description leaves the agent guessing about scope and applicability.

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 100%, so the schema carries the parameter burden and a baseline 3 applies. The description adds no parameter meaning beyond the schema, and notably does not resolve the confusing presence of items-endpoint-only fields on a traits tool.

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?

Names the resource (an OpenSea collection's trait types and values) and the payload characteristic (per-value item counts), so an agent knows it's a trait-inventory read rather than a listing or item fetch. It does not, however, distinguish itself from siblings like opensea_collection, opensea_collection_items, or opensea_collection_trait_offers.

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?

There is no when-to-use or when-not-to-use guidance, and no mention of the alternative collection/item tools. The schema further muddies this by including many 'Items endpoint only' parameters (traits, max_price, listed_only) that appear irrelevant to a trait-inventory call, with no description text explaining which apply.

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