get_spot_borrow_quota

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

With no annotations provided, the description carries full responsibility for behavioral disclosure. It merely states 'Get spot borrow quota' without explaining whether the operation is read-only, what the quota represents (e.g., maximum borrowable amount), or any side effects. This minimal disclosure leaves the agent underinformed about the tool's behavior.

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, using two sentences plus a structured Args section. It efficiently conveys essential information without superfluous content, though it could be slightly more structured with a return value note.

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 output schema, the description should explain what the tool returns (e.g., a numeric quota value). It omits this, leaving the agent uncertain about the response format. For a simple lookup tool, the description is partially complete but lacks return context.

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 to the parameters beyond the input schema, which only provides titles. It explains 'symbol' with an example (BTCUSDT) and 'side' as 'Buy or Sell', clarifying their purpose. Since schema description coverage is 0%, the description effectively compensates for this gap.

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 'Get' and resource 'spot borrow quota for margin trading,' making the purpose unambiguous. However, it does not explicitly distinguish from similar sibling tools like 'get_spot_margin_max_borrowable' or 'get_spot_margin_coin_state', so differentiation is implied rather than stated.

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 no guidance on when to use this tool versus alternatives such as 'get_spot_margin_max_borrowable' or other margin-related tools. It lacks any context about prerequisites, side effects, or conditions that would help an agent decide appropriateness.

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