getRiskLimit

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

With no annotations, the description discloses supported products, pagination (cursor-based), authentication requirement (none), and returned data (tiered risk limits, margin requirements, leverage caps). Lacks detail on pagination limit defaults or error handling, but sufficient for core behavioral transparency.

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?

Well-structured with bullet points, front-loaded purpose, and clear sections. Repetition of 'category is required; symbol is optional' appears twice, but overall concise and each sentence adds value.

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?

No output schema exists, so description must compensate. It states returns all risk tiers and includes margin requirements and leverage caps, but lacks detail on response structure, error conditions, or pagination behavior. Adequate for a query tool but not exhaustive.

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 description must compensate. It explains category (required), symbol (optional), and mentions cursor-based pagination but does not describe cursor parameter usage or effects. Provides enough context for two of three parameters, leaving cursor partially explained.

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 queries tiered risk limit parameters for perpetual and futures contracts, listing specific parameters (position size limits, margin rates, leverage). It distinguishes from sibling tool getInstrumentsInfo by explicitly stating not to use for instrument-level leverage filter.

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 clear use cases (before large positions, check max leverage, margin rates) and explicitly states when not to use (instrument-level leverage filter) with alternative tool name. Agent hint reinforces usage before setting leverage or large orders.

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