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

Annotations already establish read-only safety (readOnlyHint=true), and the description adds non-obvious call-time behavior: the tool is v4-exclusive and omitting chainId makes it span every supported v4 chain. Listing the tracked metrics also sets expectations for response content, and nothing in the description contradicts the 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?

Three sentences, each earning its place: version constraint front-loaded, purpose stated next, usage examples and chain behavior at the end. No filler; the only nit is 'v4' appearing in both the first sentence and 'Aave v4' in the second.

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 conveying what the call returns, and naming the four tracked metrics largely covers it. It doesn't describe the exact response shape or window granularity, but the schema already enumerates all window values and parameters, so nothing needed for a correct call 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 description coverage is 100%, so the baseline of 3 applies and the description need not restate parameter docs. The chainId-omission guidance mirrors what the schema already says ('Omit the argument entirely to cover every chain'), adding no net-new parameter meaning beyond schema.

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 operation — retrieving a single wallet's historical progression of net worth, supplied, debt, and health factor over a configurable window on Aave v4. The temporal framing ('over time', 'over a window') cleanly separates it from snapshot-oriented siblings like get_user_summary and get_user_positions in the sibling list.

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?

Gives concrete question types the tool answers ('how has my position changed', 'how close to liquidation a wallet has been'), which tells an agent when to invoke it. It does not name the alternative (e.g., get_user_summary for a current snapshot) or state exclusions, so it stops short of explicit when/when-not guidance.

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