supply

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

The description adds significant behavioral context beyond annotations: returns a jToken balance, typical energy and bandwidth costs, and prerequisite approval for TRC20. Annotations indicate destructiveHint and not idempotent, consistent with a deposit operation.

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 concise (4 sentences) and well-structured: purpose, prerequisite, return value, cost info. It is front-loaded and contains no redundant text.

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 complexity of a financial transaction tool with no output schema, the description covers purpose, prerequisites, return value, costs, and references an estimation tool. It could be improved by explaining error cases or authorization details, but it is largely complete.

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 100% with clear descriptions for amount (example format), market (jToken symbol), and network (optional, default mainnet). The tool description adds no additional parameter semantics beyond the 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?

The description clearly states the action ('Supply (deposit)'), the resource ('JustLend market'), and the purpose ('earn interest'). It distinguishes the tool from siblings like borrow, withdraw, and repay by specifying the deposit operation.

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 explicit guidelines: requiring approve_underlying for TRC20 markets, direct TRX for jTRX, and referencing estimate_lending_energy for cost estimation. It does not explicitly state when not to use the tool, but the sibling context from tool names provides differentiation.

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