ordinals_p2p_get_trade

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

With no annotations, the description carries full behavioral burden. It usefully discloses the return contents (counters, transfer history, status) and that no wallet is needed, but never explicitly states this is a pure read-only operation or what happens when the trade_id does not exist.

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-loaded with the core action and return contents in two tight sentences. The trailing 'earning_opportunities' cross-promotion is tangential to the task and slightly dilutes focus, keeping it from a 5.

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 simple one-parameter read tool with no output schema, the description explains return contents and the no-wallet precondition, which is sufficient. Minor gaps around not-found behavior and read-only confirmation prevent a 5.

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 100% and the single trade_id parameter is documented in the schema as 'Numeric trade ID'. The description adds no format, range, or sourcing detail beyond 'single trade', so baseline 3 applies.

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 ('Fetch full details') and resource ('single trade from the ordinals P2P ledger'), and the singular emphasis distinguishes it from list_trades/my_trades siblings. It stops short of naming an alternative explicitly, so a 4 rather than 5.

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?

'No wallet required' gives a useful precondition (no auth needed) and the singular scope implies use when you have one trade_id. However there is no explicit statement of when to prefer this over ordinals_p2p_list_trades or my_trades, nor any failure/exclusion guidance.

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