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. The description adds the trait-scoping behavior, but says nothing about pagination, rate limits, or return shape beyond what structured fields provide.

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 front-loaded sentence with no filler; the scope distinction is stated first. It is efficient but arguably too terse for a 12-parameter tool, leaving room for one clarifying clause.

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?

For a 12-parameter tool centered on trait-scoped offers, the description never explains how a trait value is specified, and the schema's 'traits' parameter is oddly labeled 'Items endpoint only.' Given the missing linkage between the tool's stated purpose and its parameters, the description is incomplete despite the output schema covering returns.

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 baseline is 3. The description adds no parameter meaning beyond the schema, and notably never connects the trait scoping to the 'traits' parameter, leaving that linkage implicit.

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 states a specific resource (OpenSea offers) and its scope (a specific trait value), and implicitly contrasts it with whole-collection offers via 'rather than the whole collection.' It does not name the sibling tool (opensea_collection_offers), but the scope contrast makes the distinction inferable.

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 only implied through the contrast with whole-collection offers; the description never states when to pick this over opensea_collection_offers or what inputs are needed to scope by trait. No explicit alternatives or exclusions are given, so the agent must infer the choice.

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