q402_yield_reserves

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

With no annotations provided, the description fully carries the burden: it states 'No auth required and no funds move - this is purely a preview of available yield', discloses it reads curated markets on BNB/Base, and clarifies the optional chain filter behavior. This is excellent transparency for a read-only tool.

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?

Front-loaded with action and safety, then return fields, scope, alternatives, parameter usage, and trigger scenarios. It is longer than strictly necessary but every sentence adds relevant context; a slight trim would make it a 5.

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 simple read-only list tool with one optional parameter and no output schema, the description fully covers purpose, safety, returned fields, supported chains, filtering, and when to invoke it. It leaves no significant ambiguity.

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 only parameter `chain` is fully described in the schema (enum+description), and the tool description adds filtering semantics ('omit it to see every supported chain') and chain-to-asset coverage (USDC/USDT vs USDC only), helping the agent decide parameter values.

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?

Description opens with 'READ-ONLY - list the Q402 Yield lending markets the Agent Wallet can supply into', a specific verb+resource+scope. It enumerates returned fields and distinguishes from siblings by stating it's a preview of available yield rather than a deposit/withdraw or positions tool.

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?

Provides explicit trigger phrases ('where can I earn yield?' or 'what's the lending APY on <asset>?') and says to use it 'before supplying', while referencing deposit/withdraw tools. However, it does not explicitly mention q402_yield_positions for viewing current holdings, so exclusion guidance is slightly incomplete.

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