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

No annotations are provided, so the description bears the full burden of behavioral disclosure. It communicates the data returned and hints at a read-only nature through the term 'position', but it omits key behavioral traits: whether it works only for wallets with existing Aave positions, what happens for wallets without positions, supported chains, rate limits, and authentication requirements. The return-value content is covered by the output schema, but limitations and edge-case behavior are not disclosed.

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 two sentences and front-loads the core purpose before appending the use case. It is efficient overall, though the first sentence packs a long list of metrics and the second sentence is slightly tacked on. Every clause provides useful information, so it earns its length.

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?

The tool is simple (2 parameters, 1 required) and has an output schema that covers return values, so the description need not explain those. However, it lacks essential context for correct invocation: chain parameter semantics (allowed values beyond default) and clearer usage guidance. The description is adequate but leaves gaps that an agent would need to resolve before calling confidently.

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 0%, and the description does not mention either parameter. The phrase 'any wallet' loosely suggests the address parameter represents a wallet address, but the 'chain' parameter—including its default 'ethereum' and what chain values are valid—is entirely unexplained. With two undocumented parameters and no compensating detail in the description, this is a significant gap.

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 description names a specific resource (Aave V3 position of any wallet) and enumerates the exact metrics returned: collateral, debt, borrowing power, LTV, liquidation threshold, health factor, and liquidation distance. This is a clear verb+resource statement that no sibling tool duplicates, so an agent can identify its function without opening the 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 description includes one usage scenario ('Use for liquidation alerts'), which gives a concrete context. However, it offers no guidance on when NOT to use it, no alternatives (e.g., evm_wallet_balance or defi_lending_rates), and no prerequisites or exclusions. The usage is implied but not fully specified.

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