supply

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

Discloses return value (jToken balance), typical energy/bandwidth costs, and behavior difference for jTRX. Adds value beyond annotations (readOnlyHint=false, destructiveHint=true) by detailing cost and prerequisites.

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?

Very concise: two sentences covering purpose, prerequisite, return type, cost, and advice. Front-loaded with essential info, no wasted words.

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 no output schema, description explains return type (jToken balance). Covers prerequisites, costs, and suggests a precision tool. Complete for a deposit tool in this context.

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 has 100% description coverage for 3 parameters. Description adds context: amount is underlying, market is jToken symbol, network defaults to mainnet. Also explains TRC20 vs TRX behavior, which is not in schema.

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?

Describes a specific action (supply/deposit assets into JustLend market to earn interest). Clearly distinguishes from sibling tools like borrow, withdraw, 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?

Explicitly states when to use (to supply assets), prerequisite for TRC20 (approve_underlying), and suggests using estimate_lending_energy for cost estimation before execution.

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