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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description still adds real value by clarifying that the SOL figure is a gross deposit 'before fees' and explicitly stating 'Nothing is closed', which prevents misreading it as an action tool in a close-position workflow.

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?

A single front-loaded sentence covering the action, the resource, and the return semantics, ending with the key constraint. It is dense with em-dash clauses but every clause carries information; nothing is redundant padding.

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, the description carries the burden of describing the return and does so: positions by status, a count of closable positions, and the gross SOL deposit they hold. Minor gap is that the possible status values are not enumerated, but for a one-parameter read tool this is largely sufficient.

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?

Only one parameter, and schema coverage is 100% — the schema already states it is a base58 Solana public key and that no connection or signature is involved. The description adds no additional parameter-level meaning, so the baseline of 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?

Specific verb (read) plus a precisely scoped resource: a Solana wallet's Meteora DLMM and DAMM v2 positions. It distinguishes itself from the many check_* siblings (e.g. check_lp_fees, check_closable_programs) by naming the exact protocol and position type.

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 is implied rather than stated: 'how many can be closed now' and 'what closing them returns before fees' signal this is the pre-close inspection step. However, no alternative is named and the 'by status' phrasing is not explained as a filter or grouping, leaving the agent to infer the trigger conditions.

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