getSpotMarginTradeCoinState

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

Annotations already indicate readOnlyHint=true and openWorldHint=true. The description adds meaningful behavioral context: the unified-account restriction and the conditional behavior of returning all coin states when currency is not provided. No contradiction with annotations.

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 short, front-loaded sentences with no filler. The primary purpose appears first, and the key constraints are listed in bullet form, making the description easy to scan.

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?

For a single-optional-parameter read-only tool with annotations present, the description covers the essential facts: what it retrieves, account eligibility, and default behavior. It does not describe the return structure, but the tool is simple and the response shape is not required for correct invocation.

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 has 0% description coverage, so the description must carry the burden. It does clarify that `currency` is optional and that omitting it returns all coin states. However, it does not specify the expected format or value domain for `currency` beyond the parameter name.

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?

Description states a specific action ('Retrieve') and resource ('spot margin leverage information for cryptocurrencies'). It is clear about the tool's purpose, though it does not explicitly differentiate from the closely named sibling getSpotMarginTradeState.

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 an explicit account-type constraint ('Unified account only') and describes default behavior when currency is omitted. However, it does not mention any alternative tool or state when to choose this over similar spot-margin siblings.

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