xrp_create_nft_offer

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

With no annotations provided, the description carries full responsibility for behavioral context. It fails to disclose that this creates an on-ledger transaction, requires a private key for signing, incurs fees, or modifies NFT ownership status. The brief phrasing 'Create buy or sell offer' gives no insight into side effects or prerequisites.

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 a single, front-loaded sentence with no filler words. It efficiently communicates the core action and target in just seven words, earning its place without redundant phrasing.

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?

Given this is a transaction-creating tool with no annotations and no output schema, the description is severely incomplete. It does not mention what happens after creation (e.g., resulting transaction hash), the need for destination optionality, the impact on the NFT, or any prerequisites (e.g., holding the NFT for a sell offer). The sparse description leaves the agent without a clear picture of tool behavior.

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%, so the baseline is 3. The description adds no extra parameter meaning beyond what the schema already provides; the 'buy or sell' phrasing simply restates the flags parameter semantics ('1 for sell offer, 0 for buy'). No additional clarity about format, defaults, or interactions is offered.

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 'Create buy or sell offer for NFT' uses a specific verb ('Create'), identifies the exact resource (buy/sell NFT offer), and clearly distinguishes this from sibling tools like accept_nft_offer (accepting offers) or get_offers (retrieving offers).

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 description provides no guidance on when to use this tool versus alternatives. It does not mention that this is for creating offers, while accepting or listing offers is handled by different tools. No exclusions or alternative tool references are given.

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