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

With no annotations, the description carries the full behavioral burden and does add meaningful context: the result is an unsigned Seaport transaction, and only the offerer can submit it. It does not disclose whether cancellation is irreversible, what happens after signing, gas implications, or failure behavior, leaving significant gaps for a destructive-sounding operation.

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?

Two short sentences, front-loaded with the action and followed by the critical authorization constraint. Every sentence adds information relevant to invocation.

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 single-parameter blockchain tool with no output schema, the description gives the essential nature (unsigned tx) and authorization rule but omits chain/network context, orderHash format, and what the caller receives or should do next. It is minimally adequate but has clear gaps.

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 0% and the only parameter, orderHash, is not described in either schema or description. The description does not explain the expected format of orderHash or where to obtain it, so it fails to compensate for the missing parameter documentation.

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 states a specific action (cancel) on a specific resource (a Seaport order transaction) and scopes it to 'one of your orders.' The term 'Seaport' and 'unsigned tx' are domain-specific but reasonably clear; it is distinguishable from accept/submit_order siblings by cancellation semantics.

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 implies when to use it (to cancel your order) and notes the authorization constraint that only the offerer can send it. However, it does not explicitly compare against alternatives or state prerequisites such as order being open, chain context, or whether this replaces an on-chain cancellation.

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