accountNoConvertRepay

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

No annotations provided, so the description carries the full burden. It discloses key behaviors: using spot balance, time-based restrictions, interest calculation timing, repayment order, and currency restrictions. This is adequate for understanding the tool's operational constraints.

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 and well-structured, with a front-loaded purpose statement followed by bullet-point rules. Every sentence adds value without unnecessary detail.

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 3 parameters, no output schema, and no annotations, the description provides sufficient context for a manual repay tool. It covers core behavior, rules, and service identifier. Lacks explanation of return values or confirmation, but the tool's simplicity makes this acceptable.

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 schema has 0% description coverage, so the description must add meaning. It explains coin and amount behavior (optional, mutual exclusivity) but does not describe the repaymentType enum, leaving part of the semantics unexplained. The description adds some value but is incomplete.

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 'Manual repay without asset conversion (lossless repay)', specifying the action (repay) and resource (debt currency). It distinguishes from siblings like accountRepay by emphasizing no conversion, making the purpose specific and well-differentiated.

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 rules for when to use, such as behavior when coin is provided without amount, prohibition during 04:00-05:30, and non-acceptance of BYUSDT. While it does not explicitly state when not to use this tool versus alternatives, the context is clear enough for an agent to decide.

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