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

With annotations already marking readOnly/openWorld/destructive hints, the description adds meaningful edge-case behavior: empty result semantics, chainsNotServed caveats, v3 vs v4 response shapes, and the 'asking again returns the same nothing' idempotency note. No contradiction with annotations.

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?

The description is dense but every sentence carries distinct information, front-loading the core purpose before edge cases. No redundant restatement of the title or schema.

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 tool with no output schema, the description covers return shapes, empty-result semantics, chain coverage behavior, and the relevant sibling alternative. Nothing an agent needs to call it correctly and interpret results 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?

Schema coverage is 100%, but the description goes beyond the schema: omitting chainId covers every served chain, version changes the return shape (positions with health factor vs supplies/borrows), and user is scoped to Aave-side positions only. This materially improves an agent's ability to pass correct parameters.

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 first sentence identifies a specific verb (get), resource (wallet Aave positions), and scope (supplies and borrows on v3, v4, or both). It also differentiates from the sibling get_markets by explicitly stating what belongs elsewhere.

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 description tells the agent to omit chainId to cover every chain without looping, explains the meaning of chainsNotServed, and directs the caller to get_markets when wallet-owned balances are needed. This is explicit when-to-use and when-not-to-use guidance with a named alternative.

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