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

No annotations are present, so the description carries the full behavioral burden, and "Read from chain" explicitly signals a read-only on-chain query — a meaningful disclosure of its non-destructive nature. It also lists the emitted data (balance, share, tier, faucet bonus), though it stops short of describing failure states like empty wallets or data freshness.

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 tightly packed sentences with no filler: the first delivered the resource and return fields, the second adds the read-only note. The most important information is front-loaded and every clause earns its place.

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 read-only query with a single rigid parameter and no output schema, the description names the four key return values, which gives a mostly workable picture. However, it leaves the wallet parameter's meaning ambiguous and does not address edge cases such as the tool being queried with a wallet holding no LP position, so it is only minimally complete.

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 description coverage is 0% and the description never explains what "wallet" should be (the address? the agent's own wallet? a stored alias?) nor how the opening "Your" relates to the parameter. The description makes no effort to compensate for the bare schema: a low-coverage schema, so a clearly below-baseline score is warranted.

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 names the exact resource (liquidity standing on the APEX/XNT pool), an explicit read action, and the four data fields it returns (balance, pool share, tier, faucet cap bonus), so an agent knows exactly what this tool does at a glance. It does not explicitly distinguish itself from siblings like lp_add_build or holdings, so it stops just short of the full 5.

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?

"Read from chain" implies the natural usage context (checking an account's LP standing), but the description gives no explicit when-to-use/when-not-to-use guidance and no alternative routing to siblings such as lp_add_build. The intended pick is inferable, but only by implication, leaving the score at baseline 3.

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