repay_txn

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

The description discloses that it returns unsigned base64-encoded transactions for signing, which is a key behavioral trait. However, with no annotations, it does not mention whether the operation is safe, whether position must exist, or any side effects. It provides basic transparency but lacks depth.

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 two sentences, front-loaded with the primary action, and contains no extraneous words. Every word earns its place.

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?

The tool is moderate complexity with four parameters fully documented in the schema, and the description explains the output format. However, the lack of usage guidelines and sibling differentiation leaves room for incompleteness in a context with many similar tools.

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 input schema covers all four parameters with descriptions, so the baseline is 3. The description adds no additional meaning beyond 'repay borrowed tokens', which is already expressed in the schema. No param details are enriched.

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 builds unsigned transactions to repay borrowed tokens to a DorkFi lending market, which is specific and actionable. However, it does not distinguish between this and sibling tools like repay_on_behalf_txn or repay_all_txn, which also repay borrowed tokens.

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?

No guidance is provided on when to use this tool versus alternatives. It does not mention conditions for use, prerequisites, or exclusions. For a tool with many sibling repayment-related tools, this is a notable gap.

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