repay

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

Discloses cost (energy/bandwidth) and approval requirements, adding value beyond annotations. Does not contradict destructiveHint=true. Cost info is useful for agent planning.

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?

Three concise sentences, front-loaded with purpose. No redundant words. Every sentence adds meaningful information.

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?

Covers purpose, prerequisite, special value, and cost. Lacks details on return value or side effects, but annotations already indicate destructive nature. Adequate for this complexity.

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?

Adds context to parameters: clarifies amount 'max' usage, and links market to TRC20 approval. Schema coverage is 100%, so baseline is 3; the additional prerequisite info raises the score.

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?

Clearly states the action ('repay borrowed assets') and the target ('JustLend market'), distinguishing it from sibling 'moolah_repay'. Includes specific details like approval prerequisite for TRC20.

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?

Describes when to use (repaying borrowed assets), prerequisite (approval for TRC20), and special value 'max'. Lacks explicit comparison to alternatives, but context is clear given sibling names.

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