accept_offer

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

With no annotations provided, the description fully carries the behavioral burden. It discloses the atomic Seaport execution steps, the 1% fee deduction, the revert condition (buyer lacks WETH/approval), and the approval prerequisites for the seller. This is exceptionally transparent for a transaction tool.

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?

Although longer than average, every sentence adds necessary information. The description is front-loaded with the main purpose, then organized into execution details, fee implications, potential reverts, and prerequisites. No filler or redundancy.

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 transactional tool with no output schema, the description covers return value, execution behavior, fees, failure modes, required approvals, and references to related tools. It leaves minimal ambiguity for an agent deciding whether and how to invoke it.

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% with both parameters well-described in the schema. The description adds slight context by referencing 'offer hash' in relation to get_name_details, but does not significantly enhance understanding beyond the schema's existing property descriptions.

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 clearly states the specific action: 'Accept a standing offer on an ENS name you own' and immediately follows with the return type ('Returns unsigned Seaport fulfillOrder() calldata'). It distinguishes from sibling tools like make_offer, cancel_offer, and purchase_name by focusing on the accept-offer flow.

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 provides explicit prerequisites and cautionary guidance: requires approval on NameWrapper or BaseRegistrar, references approve_operator if needed, and instructs to use get_name_details to confirm the offer hash. It also warns about the buyer's WETH balance/approval causing reverts, giving clear when-to-use context.

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