ordinals_p2p_transfer

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

With no annotations, the description carries the behavioral burden and does well: it says the tool records to the trade ledger, marks the trade closed, and requires an unlocked wallet with Bitcoin keys. It also discloses BIP-137 signing by the active wallet, though it omits failure conditions and idempotency behavior.

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 and mostly efficient, starting with the core action and following with signing and wallet requirements. The final earning_opportunities tip does not help invoke this tool and slightly dilutes conciseness.

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 mutation-style ledger record with six parameters and no output schema, the description covers the key action, side effect, signing behavior, and wallet prerequisite. It could be stronger by explaining success/failure outcomes or expected postconditions.

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%, and the schema already explains parameters such as tx_hash being optional for sBTC/off-chain transfers. The description adds broad context about on-chain versus off-chain sBTC transfers but does not add per-parameter semantics beyond 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?

States a specific verb and resource: "Record a completed inscription transfer on the trade ledger" and clarifies that it "Marks a trade as closed." This is clearly a ledger-recording action rather than an actual transfer, though it does not explicitly distinguish itself from the ordinals_p2p_* swap/offer siblings.

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?

Provides implied usage context by saying it records a completed transfer and closes a trade, but does not state when not to use it or name alternatives such as ordinals_p2p_psbt_swap or ordinals_p2p_create_offer. The earning_opportunities tip is unrelated to selecting this tool.

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