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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered, and an output schema exists so returns needn't be re-explained. The description adds the scope (collections held by the wallet) and the projected fields, but says nothing about auth needs, pagination behavior, or rate limits. Adds some value on top of structured data, not a lot.

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, zero waste: the purpose and returned fields are front-loaded, and the sibling-routing guidance follows. Each sentence earns its place.

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 annotations covering safety, a full output schema, and 100% parameter coverage, the description only needs purpose and routing, both of which it delivers. It is nearly complete, with only minor scoping nuance (e.g. pagination expectations) left implicit.

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 every parameter (limit, cursor, sort_by, identifier, event_types, sort_direction) is documented in the schema itself. The description adds no parameter syntax or format detail beyond what the schema provides, so the 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 verb ("List") and resource ("collection records held by an OpenSea wallet") plus the salient fields returned (item count, total quantity, floor price). It clearly distinguishes itself from opensea_profile_items and opensea_profile_created without needing to open the schema.

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?

Explicitly names both alternative siblings and the condition that selects each ("for individual holdings" and "for collections the wallet created"), so an agent can route correctly between the three profile tools. Little is left to inference.

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