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

Annotations only say destructiveHint=true, but the description adds rich behavioral context: names are swept cheapest-first across NameWhisper, OpenSea, and Grails; packed into one fulfillAvailableAdvancedOrders call; capped at 20 names; sold-out orders are skipped; excess is refunded; and NFTs are delivered directly. It also discloses the response contents, which matters given there is no output schema.

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 description is longer than average but every sentence earns its place: it covers intent, usage trigger, cohort selection, bounds, transaction mechanics, cap, skip/refund behavior, and response summary. It is front-loaded with the core behavior and uses structured sub-clauses instead of fluff.

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 complex financial transaction tool with 9 parameters and no output schema, the description is complete: it tells when to use it, how to select the cohort, how to bound the sweep, what happens under the hood, why it is capped, and what the response reports. No significant operational gap remains.

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 value by explaining how parameters work together: category/q/charType/minLength/maxLength define the cohort, count and maxBudgetEth bound the sweep, and maxPriceEth caps per-name price. It also clarifies algorithm behavior like 'keeps buying up the floor until adding the next cheapest would exceed this.'

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 opens with a specific action: 'buy the CHEAPEST N listed ENS names in a category/collection (or matching a filter) in ONE Seaport transaction.' It also explicitly differentiates from batch_purchase, which is used for specific names, so an agent can distinguish it from the closest sibling without inspecting schemas.

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?

The description explicitly states when to use the tool: 'Use this when the user wants "the cheapest N", "sweep the floor", or "buy up to X ETH of" a cohort.' It also names the alternative: 'rather than naming specific names (that's batch_purchase).' This gives clear selection criteria.

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