batch_create_listings

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

With no annotations, the description carries the full burden. It discloses the return type (unsigned Seaport OrderComponents), the need to POST signatures to a URL, per-name error collection with partial success, and the operator approval requirement. This is rich behavioral context beyond the basic input 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?

Each sentence adds value: purpose, return type, workflow, platform scope, comparison, error handling, prerequisite. The description is well-structured and front-loaded with the core purpose, with no filler.

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?

Despite having no output schema, the description explains the return format and the subsequent action required. It covers error handling, prerequisites, and the full workflow, making it complete for a tool of this complexity.

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 each parameter already has a description. The tool description does not add new parameter-level semantics beyond what the schema states, so baseline 3 applies.

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 verb+resource: 'Bulk-list up to 10 ENS names for sale on NameWhisper in one signing flow.' It clearly distinguishes this from the sibling create_listing by emphasizing the batch aspect and the single-signing-flow UX.

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 explicitly compares to create_listing, stating 'Cheaper UX than calling create_listing in a loop (one wallet popup vs N).' It also notes 'NW-native only' and the operator approval prerequisite, giving clear guidance on when to use this tool versus alternatives.

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