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

With no annotations, the description carries the full burden of behavioral disclosure. It only states the output (balance & sequence) but does not mention error handling for invalid addresses, rate limits, required authentication, or response format nuances. The description adds no behavior beyond the basic function.

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 extremely concise, consisting of a single short phrase. While it is not verbose, it sacrifices necessary detail for brevity. It lacks a full sentence structure and omits key information, so it does not earn a higher score for conciseness.

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, no annotations, and an output schema (which we cannot see), the description is incomplete. It fails to explain the input parameter, any prerequisites, or edge cases. The presence of an output schema does not excuse the lack of parameter documentation and usage context. An agent cannot confidently call this 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 parameter 'q' with no description and zero schema coverage. The description does not explain that 'q' is an XRP address or its expected format (e.g., r-prefix). Since the description fails to compensate for the missing schema documentation, the parameter semantics are completely unclear.

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 identifies the resource (XRP Ledger account) and the information returned (balance & sequence). It implicitly differentiates from sibling crypto tools like btcaddr and ethaddr by specifying XRP, though it does not explicitly name alternatives. The verb is implied ('get' or 'lookup'), but the purpose is understandable.

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 is provided on when to use this tool versus alternatives. There is no mention of conditions for using XRP-specific lookup versus other address tools, nor any exclusion criteria. The agent must infer usage from the name and context, which is insufficient for a tool with many siblings.

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