Coinglass: getCoinglassBitfinexMarginData

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the description's simple 'provides data' is consistent but adds no additional behavioral context. It does not disclose pagination limits, data freshness, or whether historical data is available. With high annotation coverage, this is acceptable but not revealing.

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 a single sentence of 13 words. It is front-loaded with the core data type ('data on margin long and short positions') and source ('from Bitfinex'). No wasted words.

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 ideally hint at the return type (e.g., list of positions, with long/short ratios). It only states 'data on margin long and short positions', which is vague. The tool has moderate complexity (3 params, no enums), so the description is minimally adequate but could specify whether results are historical or current, and the structure of each position.

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?

Input schema has 100% description coverage for all three parameters, so the description's role is minimal. It does not add semantics beyond the schema, which already explains 'symbol', 'page', and 'limit'. The baseline score of 3 applies.

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 it provides 'margin long and short positions from Bitfinex', using a specific verb ('provides') and resource ('margin long and short positions from Bitfinex'). It distinguishes itself from sibling tools like 'getCoinglassBitcoinEtfList' which deal with ETFs.

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 does not state when to use this tool or when not to. It merely describes what it does, leaving the agent to infer usage context. No alternatives or exclusions are mentioned.

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