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

No annotations exist, and the description provides no behavioral details—no mention of read-only nature, API calls, potential side effects, or data sources. It's merely a headline.

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 7-word fragment, not a proper sentence. It's concise but under-specifies the tool's purpose and behavior.

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 tool with one parameter and no output schema, the description still leaves the tool's operation and return value entirely unclear. It doesn't convey enough for an agent to select and invoke the tool correctly.

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 defines a single 'address' parameter, but the description doesn't mention it or explain what address should be provided. With 0% schema description coverage, the description should compensate but offers no parameter semantics.

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 the noun phrase 'escrow intelligence' rather than an action verb. It lists output data points but doesn't state what the tool does (e.g., 'retrieve' or 'monitor'). Among siblings (xrpl_escrow_check, xrpl_escrow_create), it doesn't differentiate.

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 guidance on when to use this tool vs alternatives. It doesn't mention any context, prerequisites, or when to use it over xrpl_escrow_check or other tools.

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