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

With no annotations, the description carries the full burden and does add real behavioral context: it is a live blockchain read ('It queries the blockchain') with an explicit latency warning ('takes a few seconds'), and it discloses the shape of the returned values. It does not state auth/wallet-connection prerequisites or any error/caching behavior, which is the remaining gap.

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 sentences, fully front-loaded: what it returns first, the latency caveat second. No filler, no repetition of the tool name.

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?

No output schema or annotations exist, so the description must cover returns — and it does, naming supplied/borrowed/net/health factor plus the protocol and chain coverage. What is missing is how the user's wallet is selected (no params, no auth note) and any failure mode, leaving a small but real gap for a zero-config read 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?

The tool takes zero parameters, so per the rubric the baseline is 4. The description usefully clarifies that the wallet is implicit ('The user's lending positions') rather than supplied as an argument, which is the only semantic question a param-less schema raises.

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?

Names a specific verb+resource ('lending positions'), enumerates the exact protocols (Aave V3, Spark, Compound V3, Morpho, EigenLayer) and chains covered, and lists the returned fields (supplied, borrowed, net, health factor). An agent can distinguish this from get_portfolio or get_pnl without opening any schema.

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 DeFi/lending scoping implies when to reach for this over a generic portfolio call, but no explicit when-to-use statement or sibling alternative is named (e.g. get_portfolio for CEX balances). Usage is inferable rather than stated.

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