get_pending_offers

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

With no annotations provided, the description carries the full burden. It reveals behavioral context by listing the types of operations returned, including paid-but-not-yet-minted orders the user can still complete. However, it does not explicitly state whether the operation is read-only, mentions any side effects, auth requirements, or rate limits, so transparency is partial.

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 compact yet packed with information. It front-loads the core purpose, then gives concrete usage triggers and a parameter hint, all in two sentences. No redundant or wasted words.

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 the tool's simplicity (one parameter, no output schema), the description provides enough context: it specifies the return categories and when to use it. It stops short of describing the exact structure of each offer, but for an agent selecting and invoking the tool, it is sufficiently complete.

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% for the only parameter (address), which includes an example. The description echoes the address requirement but adds no new semantic meaning beyond what the schema already provides. Baseline 3 is appropriate.

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 uses a specific verb and resource ('Get all pending XRPL domain operations') and further clarifies the three included categories: incoming offers, outgoing offers, and paid-but-not-yet-minted orders. This clearly distinguishes it from sibling tools like check_tx_status or get_portfolio.

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 explicitly states when to use the tool with example user queries ('do I have any pending transfers?', 'what offers are waiting on me?') and before suggesting accept/cancel/continue-mint actions. It lacks explicit 'when not to use' or named alternatives, so it falls short of a 5.

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