accountRepay

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

No annotations are provided, so the description fully carries the burden. It discloses many behavioral traits: repayment logic (full vs partial), conversion fees, time restrictions, and priority ordering of liabilities. This is exceptionally transparent.

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 well-structured with bullet points and front-loads the purpose. However, it is somewhat lengthy; some details (e.g., conversion fee limits) could be condensed without losing essential 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?

Given no annotations and no output schema, the description is remarkably complete. It covers input semantics, behavioral rules, side effects (conversion, fees), and temporal constraints. An agent has sufficient context to use the tool correctly.

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 coverage is 0%, so the description must compensate. It explains the meaning of coin and amount through rules (e.g., 'If neither coin nor amount is provided, the system repays all liabilities'), but it does not describe the repaymentType parameter (enum: ALL, FIXED, FLEXIBLE). Partial coverage leaves gaps.

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 'Manually repay the liabilities of Unified account' with a specific verb and resource. However, it does not explicitly distinguish this tool from sibling tools like accountNoConvertRepay or quickRepayment, which have overlapping purposes.

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 detailed rules about when to use coin/amount parameters and lists blocking conditions (e.g., time block). However, it does not guide the agent on when to choose this tool over alternatives like accountNoConvertRepay or quickRepayment.

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