t2000_repay

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

Given no annotations, the description covers key behaviors: repayment of debt, targeting specific assets or highest-APY, all-debt repayment, and dryRun preview. It does not disclose side effects like transaction execution or balance updates, which would be beneficial.

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?

Two sentences with no extraneous words. Front-loaded purpose, then parameter guidance. Highly efficient.

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, parameter usage, and preview mode. Adequate for a repayment tool with 3 params and no output schema. Missing details on transaction outcome or error states, but not critical given brevity.

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 description adds significant meaning beyond schema descriptions: asset omission behavior, 'all' for amount, and dryRun as preview mode. Schema coverage is 100%, and the description enriches each parameter's semantics.

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 verb 'repay' and the resources 'USDC' or 'USDsui'. It also specifies behavior for omitted asset (highest-APY) and 'all' to repay entire debt, distinguishing it from other tools like borrow or withdraw.

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 instructions on when to pass asset, omit it, or use 'all', plus the dryRun option. However, it lacks explicit when-not-to-use or differentiation from sibling tools beyond the core action.

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