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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered; the description adds genuinely useful context beyond them: the data source (Aave v3 on Base, read on-chain) and a metered cost (0.0050 USDC per call, first free). It does not disclose behavior for unlisted assets or failure modes, keeping it short of a 5.

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 tight sentences, front-loaded with protocol, chain, and returned data, followed by the pricing constraint. No filler, and every clause carries information the agent needs.

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 single-optional-parameter read tool with no output schema, the definition covers source, scope, default, and cost adequately. It could still say what happens for an unlisted asset or give units/format for the fee, which is why it is not a 5.

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?

With one optional parameter and 100% schema description coverage, the schema already documents asset as an ERC-20 address defaulting to WETH. The description only restates the default asset value, adding no format or edge-case detail beyond the schema, 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 resource (flash-loan liquidity and fee), the protocol (Aave v3), the chain (Base), and the access mode (read on-chain). An agent can instantly tell this returns flash-loan data rather than anything in the sibling set (contract-profile, dex-arbitrage, liquidity-health, etc.).

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 only implied: the description makes clear it returns liquidity/fee data, so the agent can infer it is used when sizing or pricing a flash loan, but there is no explicit when-to-use, no prerequisites, and no alternative named among the siblings.

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