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

The annotations already mark this as a destructive, non-idempotent write, but the description adds substantial behavior: Seaport atomically pulls WETH, transfers the ENS name, deducts fees, and reverts if the buyer lacks WETH balance or allowance. It also explains wrapped-name handling and ENS v2 role requirements, which an agent could not infer from the annotations alone.

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 front-loaded with the action and output, then uses a short bullet list to explain atomic behavior before covering prerequisites and edge cases. Despite its length, every section serves the high-complexity transaction and no sentence is merely decorative.

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 no output schema, the description fully carries the burden: it explains that the response is unsigned calldata and references response fields such as approvals and nftApproval. It also covers the destructive transaction path, revert risks, wrapped-name handling, and ENS v2 role invalidation, so an agent has enough context to call it correctly.

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%, so the baseline is 3, but the description still adds operational meaning for both parameters: orderHash should be confirmed via get_name_details, and walletAddress must own the name and hold every role on it. That is useful validation context beyond the schema, though it does not add format details.

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 first sentence gives a specific verb, resource, and scope: accept a standing offer on an ENS name you own. It also states the concrete output, unsigned Seaport fulfillOrder() calldata, which distinguishes it from make_offer, cancel_offer, and purchase_name.

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 names prerequisites and alternatives: unwrap_name before accepting a wrapped name, approve_operator for Seaport approval, get_name_details to confirm the highest offer, and WETH allowance steps. It also states when an offer can no longer be accepted if roles changed, leaving little ambiguity about when and how to use the tool.

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