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

The description adds valuable behavioral context beyond the annotations: it explicitly discloses that no signing, posting, or broadcasting occurs. This complements the readOnlyHint and makes clear the tool returns prepared actions rather than mutating chain state. There is no contradiction with the annotations.

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 extremely concise and front-loaded: one sentence states the core action and a second clarifies the key boundary. No filler or redundant phrasing exists.

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 description covers the tool's core job and behavior limitations, and the output schema plus annotations carry some of the required detail. It is incomplete regarding sibling differentiation and exact network/marketplace context. An agent may not know whether to pick `prepare_listing` over `prepare_mainnet_listing` or `prepare_internal_listing` without further inference.

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 high (83%), and the description itself does not add parameter-specific meaning beyond the schema. The parameter semantics are mostly well documented already, so a baseline 3 is appropriate; the description adds no notable benefit for parameters.

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 verb ('prepare'), the resource ('exact OpenSea approval and Seaport listing actions'), and the target ('one NFH'). It also adds an important boundary: 'Never signs, posts, or broadcasts.' However, it does not explicitly name or distinguish itself from sibling tools like `prepare_mainnet_listing` or `prepare_internal_listing`, so some ambiguity remains.

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 usage context is somewhat implied: this tool should be used when the agent must create an OpenSea/Seaport listing without actually executing it. 'Never signs, posts, or broadcasts' gives a useful negative signal, but there is no explicit when-to-use guidance, no exclusion list, and no named alternative among the many `prepare_*` siblings.

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