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

Annotations already cover the read-only, idempotent, non-destructive, open-world profile, and the description adds substantial context beyond them: the methodology (collateral discounted and debt marked up by volatility ratio), data sources (positions from the contract, prices from NEAR Intents), and a detailed pricing/auth model (x402 on Base, $0.02/call, prepaid x-credit-token header for unlimited, 1 free call/day, no API key). This is exactly the behavioral detail an agent needs before invoking a paid endpoint.

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?

Purpose and scenario are front-loaded, and the trailing pricing/auth sentence earns its place given the x402 payment model. It is a dense single paragraph rather than a structured list, which slightly impairs scanability, but there is little true filler.

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?

Output schema exists, so return values need not be explained, yet the description still previews the key outputs (collateral and debt in USD, distance-to-liquidation, GO/HOLD/STOP). Combined with the data-source and payment details, an agent has everything needed to call it 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?

Schema coverage is 100% for the single 'account' parameter, so the schema itself documents the input adequately. The description only restates 'Required input: account' without adding format or derivation detail beyond the schema's 'NEAR account', so the baseline 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?

States a precise verb+resource: the health factor of an account's Rhea Lending (Burrow) position on NEAR, computed as the contract does. This is specific enough to distinguish it from siblings like morpho_health, position_health, and exit_liquidity without opening any schema.

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 opening question ('How close is this position to liquidation?') frames the scenario in which the tool applies, and naming Rhea Lending/NEAR implicitly scopes it away from other chain lending tools. However, it never explicitly states when to use this versus a sibling such as position_health or morpho_health, nor any prerequisites or exclusions.

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