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

No annotations are provided, so the description carries the full burden and does it well: it discloses read-only status, that the record is rebuilt by walking a wallet's full Solana transaction list (implying cost/latency), that totals are recomputed rather than stored, and that individual deposits are withheld. It stops short of stating latency or rate limits explicitly.

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 rug-check framing are front-loaded, followed by the return-field distinctions. It is long but most sentences carry substantive meaning for a complex tool, though the single dense paragraph could be tightened.

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 output schema and no parameters, the description compensates fully by explaining the key return semantics (lock.allLocked, builtIntoLiquidity, positionNow, feesCompounded, readAt/positionReadAt/pricedAt), what is omitted, and where the full record lives. Nothing essential to calling it correctly is missing.

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 tool takes zero parameters, so the baseline is 4. The description correctly treats the tool as parameterless and instead invests in explaining the returned fields, which is the right allocation of effort.

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 and resource and frames the exact question it answers ('can they rug this'), which is a distinct angle from siblings like get_proof_of_reserves, get_lock_tier, or get_project_treasury. An agent can tell what this tool returns and why it differs from the other liquidity-adjacent tools.

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 framing 'answers the question behind can they rug this' implies the use context, but there is no explicit when-to-use-vs-alternative routing or when-not guidance. With 37 siblings, naming a comparison tool would have helped; usage must be inferred.

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