setAutoRepayMode

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

The description thoroughly explains behavioral details: repayment timing (0 and 30 minutes every hour), repayment amount calculation (min of available spot balance and current liability), and the effect of omitting the currency parameter (applies to all currencies). Since no annotations are provided, this context is essential and well-covered.

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 structured with a clear opening statement, followed by a detailed explanation and bullet points for currency behavior. It is concise (about 100 words) and avoids unnecessary repetition. Minor improvement could be merging the timing and amount details into a single paragraph.

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 description covers the core functionality and parameter behavior well. However, it does not mention the return value or error cases (e.g., what happens if autoRepayMode is invalid or currency not found). For a tool with no output schema, this information could improve completeness.

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 has 0% description coverage, but the tool description adds value by explaining the meaning of autoRepayMode ('1' enables, '0' disables) and the behavior when currency is omitted (applies to all currencies) versus specified (only that currency). This clarifies parameter usage beyond the raw schema.

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's purpose: 'Set spot automatic repayment mode.' It explains the mechanism (timed repayments at 0 and 30 minutes each hour) and distinguishes itself from sibling tools like accountRepay (manual repay) and getSpotMarginTradeAutoRepayMode (query) by focusing on enabling/disabling auto-repay.

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 implies when to use (to enable or disable automatic repayments) but does not explicitly contrast with alternatives like manual repay (accountRepay) or querying the current mode (getSpotMarginTradeAutoRepayMode). No when-not-to-use guidance is provided.

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