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

Annotations only declare readOnlyHint and openWorldHint; the description adds substantive context beyond them — 'reads only, signs nothing', a live on-chain read, and the default-target wallet address. It also enumerates what the read produces, so behavioral expectations are well set.

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?

Front-loaded and information-dense, with the core action stated first and no wasted sentences. It is somewhat ornate ('Rebalancing, the free half') and packs everything into two very long clauses, but every clause carries operational content.

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 return-value burden and does so — it lists in-range status, room to each edge, holdings, BNB value, fees owed, and gas economics. Combined with the read-only scope and input fallback, an agent has what it needs to call and interpret this tool.

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%, so the baseline is 3; the description adds meaning beyond the schema by disclosing the fallback behavior (no id/wallet → reads the agent's own position) and clarifying the dual 'wallet'/'address' input path, which the schema alone does not convey.

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 a specific verb and resource — 'look at a PancakeSwap V3 liquidity position on BNB Chain' — and scopes it as a read ('read from the chain now', 'Reads only, signs nothing'). The phrase 'the free half' gestures at the sibling lp_position_plan without ever naming it, so sibling differentiation is implied rather than explicit.

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?

It gives concrete invocation conditions: 'Give a position id or a wallet that holds one; with neither, it reads the position this agent runs itself' and even supplies the fallback address. That is clear when-to-use guidance for each input path, but there is no explicit when-not-to-use or named alternative to route to.

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