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

Annotations already cover the safety profile (readOnlyHint, openWorldHint), and the description adds genuinely useful behavioral context beyond them: the read is on-chain, the per-call price is 0.0050 USDC, and the premium is always paid. It does not mention rate limits or latency, but the pricing disclosure is meaningful added value.

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 compact sentences, front-loaded with the tool's purpose and chain/scope. The pricing sentence is relevant and brief; little waste, though it is somewhat dense with clauses.

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, single-optional-param tool with annotations covering safety and no output schema, the description conveys what is returned (liquidity and fee) and the default asset. Slightly more on the return shape would round it out, but nothing essential 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% and the schema documents the single optional asset param with its WETH default. The description's 'default WETH' and 'any listed asset' restate the schema rather than adding new meaning, so the baseline 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?

States a specific verb+resource: reads Aave v3 flash-loan liquidity and fee for any listed asset on Base. This is a distinct resource (flash-loan availability/cost) that is clearly separable from siblings like aave-yield or liquidity-health.

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 – an agent can infer you call this to check flash-loan capacity or fees, but there is no explicit when-to-use, when-not, or routing to alternatives such as aave-yield or liquidity-health.

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