xrp_get_escrows

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

With no annotations provided, the description bears full responsibility for disclosing behavioral traits. It only states that it retrieves escrows and does not mention whether it is a read-only operation, whether it requires authentication, or what pagination or response format to expect. The term 'get' weakly implies a read but offers no concrete behavioral details.

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 unnecessary words or repetition. It communicates the core function efficiently, though the brevity comes at the cost of behavioral detail.

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?

The tool is simple (one parameter, no output schema, no annotations), and the description specifies the basic function. However, it does not clarify what an escrow is, what the return payload looks like, or whether pagination applies when retrieving 'all' escrows. Thus, it is minimally complete but lacks detail for an agent to fully anticipate the response.

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?

The schema fully describes the single parameter ('address' as 'Account address'), and the description's 'for an account' adds no new meaning beyond the schema. Therefore, the description does not enhance understanding of the parameter's purpose or format.

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 clearly states the verb ('Get'), the resource ('escrows'), and the scope ('for an account'). This distinguishes it from sibling tools that create, finish, or cancel escrows, and from other retrieval tools like xrp_get_offers or xrp_get_ledger_entry.

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 excluded scenarios, alternative tools, or prerequisites. The appropriate use case is implied by the verb and resource, but there is no explicit direction.

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