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

Annotations cover the safety profile (readOnly, openWorld, non-idempotent), and the description adds real value beyond them: it specifies that verification is live and anchored to a validated ledger, and warns that a closed signing path is an observation at one ledger rather than a permanence guarantee. It also notes the account role is an owner-confirmed declaration, which qualifies the reliability of the verdict.

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?

Two sentences with no filler; the enumeration of outputs is front-loaded and the caveat follows. The first sentence is dense with clauses but each clause carries distinct information.

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?

With no parameters and no output schema, the description carries the burden of explaining what comes back, and it does so (balances, share, pro-rata values, control assessment, verdict). The ledger-pinning caveat also sets expectations correctly. Only the absence of any sibling/timing guidance keeps it from full completeness.

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?

Zero parameters and 100% schema coverage, so the baseline is 4. The description necessarily adds nothing about inputs because there are none to describe.

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 specific verb (verify) and resource (LP-lock accessibility for the ASTEROID/XRP AMM), and enumerates the concrete outputs: LP balance, share of supply, pro-rata implied XRP/ASTEROID, per-account control assessment, and an overall verdict. It is distinguishable from siblings like get_liquidity_state and get_liquidity_stats, though it never names them or explicitly contrasts the distinction.

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 context is implied (this is the live LP-lock verification tool) but there is no explicit when-to-use, when-not-to-use, or alternative routing versus get_liquidity_state/get_liquidity_stats. The caveat about closed signing paths is interpretive guidance rather than invocation guidance.

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