get_v4_user_supplies

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

With no annotations provided, the description carries full burden for behavioral disclosure. It only states 'No API key needed', which addresses authentication. However, it does not confirm the tool is read-only, describe any side effects, or mention rate limits or data freshness. More behavioral context is needed for safe agent usage.

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 a single sentence of 17 words, front-loaded with the main action. Every word contributes meaning without redundancy. It is highly concise and structured well for quick parsing.

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?

Given the tool's simplicity (2 parameters, no output schema, no annotations), the description is minimally adequate. It states the purpose and authentication requirement but lacks details on return format, error handling (e.g., invalid address), or behavior when no supplies exist. More completeness would improve usability.

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 coverage is 100% with descriptions for both parameters (chainId as filter, userAddress as EVM address). The description adds no additional parameter semantics beyond the schema, and the mention of 'principal, interest, and collateral status' refers to output, not input parameter meaning. Baseline score of 3 is appropriate.

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 the tool retrieves a user's Aave V4 supply positions, specifying the included data (principal, interest, collateral status). The verb 'Get' and resource 'supply positions' are specific, and the tool is distinguished from siblings like get_v4_user_borrows and get_v4_user_positions by focusing solely on supplies.

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 provides no guidance on when to use this tool vs alternatives. It only mentions that no API key is needed, but does not state when not to use it, such as when borrow positions are needed instead. Given the presence of closely related siblings (get_v4_user_borrows, get_v4_user_positions), usage context is missing.

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