xrp_create_escrow

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

With no annotations provided, the description carries full responsibility for behavioral disclosure. It only states a high-level action and lock types, omitting side effects, fees, required permissions, or consequences (e.g., funds being locked). This is a significant transparency gap for a mutation-like operation.

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 without redundant phrasing or filler. It efficiently conveys the core action and key differentiators.

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 complexity (6 parameters, lock conditions, timestamps) and lack of output schema, the description is too minimal. It does not explain how escrow usage flows, what 'time' or 'condition' locking implies, or what happens upon creation, leaving the agent without critical context.

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 already provides descriptions for all 6 parameters with 100% coverage. The description adds no additional parameter-level meaning, so the baseline of 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?

The description uses a specific verb ('Create') and explicit resource ('escrow'), clearly distinguishing it from siblings like finish, cancel, or get. It also identifies the two locking modes (time or condition), which adds specificity beyond just 'create an escrow'.

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?

Usage is implied by the verb 'Create' relative to sibling tools (xrp_finish_escrow, xrp_cancel_escrow, xrp_get_escrows), but there is no explicit guidance on when to choose this tool instead of alternatives, nor any exclusions or prerequisite conditions.

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