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

With no annotations, the description carries the full behavioral burden. It does disclose a critical trait—an atomic swap of ownership for ETH—but it omits important operational details such as prerequisites (seller must be current owner, offer must still be valid), irreversibility, failure behavior, and post-acceptance effects on listings or other offers.

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 communicates the action and key outcome without restating schema property names or repeating obvious details. Every word earns its place.

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?

The schema covers all inputs and the description explains the core transaction, but for an on-chain, state-changing operation with no annotations and no output schema, it leaves gaps: no return value, no error conditions, and no explicit authorization model. It is adequate but not complete.

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 only the contextual framing 'your .i domain' and 'offered ETH' but does not provide additional parameter-level meaning or format guidance beyond what the schema already states.

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 uses a specific verb ('Accept'), a specific resource ('a buyer offer on your .i domain'), and a clear outcome ('an atomic swap of ownership for the offered ETH'). This clearly distinguishes it from sibling tools like marketplace_make_offer, marketplace_cancel_offer, and marketplace_buy_domain.

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 context is clear: this tool is for accepting an existing buyer offer as a seller. It does not explicitly name when not to use it or contrast it with closely related marketplace actions, but the described scenario is unambiguous enough for an agent to select it appropriately.

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