get_aave_user_position

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

With no annotations, the description carries full burden. It discloses that the tool returns empty arrays if no position exists, explains the health factor formula, mentions amounts in native token units requiring decimal division, and lists return fields. It doesn't mention authentication or rate limits, but these are less critical.

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 front-loaded with usage examples and concisely covers all key aspects: purpose, example queries, return fields, health factor formula, and decimal handling. Every sentence serves a purpose with no redundancy.

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 tool with no output schema, the description provides a thorough explanation of returns (supplied assets, borrowed assets, health factor, etc.), the health factor formula, and the decimal handling requirement. It is complete enough for an agent to correctly select and invoke the 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 input schema covers both parameters with descriptions (100% coverage). The description adds value by explaining the chain enum list, the userAddress format, and the behavior when no position exists (empty arrays). It also describes the output structure, which goes beyond schema requirements.

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 clearly states it returns a wallet's AAVE position including supplied assets, borrowed assets, health factor, collateral flags, and e-mode category. It provides concrete example queries, distinguishing it from siblings like get_aave_reserve or get_aave_liquidations.

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?

Explicitly says 'Use this when the user asks about a wallet's AAVE position' and gives multiple example queries. While it doesn't explicitly list when not to use, the context of sibling tools (e.g., get_aave_reserve for a single reserve) implies appropriate usage. Could be more explicit about alternatives.

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