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

Goes well beyond the annotations: prepared-not-sent semantics, returns a signRequest (summary, warnings, signLink, expiresAt 15 min, payload null), persists it for the sign page, requires a human signature, server holds no keys and submits nothing. This fully discloses the side-effect profile of a tool that is technically non-read-only.

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?

Front-loads what it does, then the mechanism, then the security model. Slightly redundant — 'Prepared, not sent' and 'nothing happens until then' restate the same idea — but no sentence is pure filler.

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?

Covers the full lifecycle (check, prepare, store, sign) and the return payload despite there being no output schema. It omits error behavior when the listing is closed or not owned, which an agent would want before calling.

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 already 100%, and the description still adds value by mapping orderHash to orderId in get_land_order_book and clarifying that wallet is the signing address. Optional slug/tokenId are left unexplained in prose but are covered by the schema.

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?

Specific verb (prepare canceling) plus precise resource (the wallet's own open listing or offer) and network (Sepolia Testnet). It also maps orderHash to its source (orderId from get_land_order_book), which distinguishes it cleanly from siblings like accept_land_offer or get_land_order_book.

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?

Explains the precondition check (order must be open and created by the wallet) and points at get_land_order_book as the source of the orderHash. It does not explicitly contrast with accept_land_offer or state what to do when the check fails, so it stops short of full when/when-not routing.

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