get_bitfinex_long_positions

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

No annotations provided, so description bears full burden. It adds minimal behavioral context beyond function name: only that data reflects bullish sentiment. Lacks details on read-only nature, update frequency, rate limits, or data staleness.

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?

Single sentence that presents action first: '获取 Bitfinex 杠杆多头持仓数据'. Every word contributes to meaning with no waste. Efficiently conveys purpose.

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, and description does not explain return format (e.g., numerical values, time series). For a data retrieval tool, lacking output structure is a significant gap. Does not adjust for complexity since parameters are simple.

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 description coverage is 100% with both parameters (symbol, timeframe) having clear descriptions. Description adds no extra parameter information beyond what the schema provides, earning baseline 3.

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 clearly states the tool retrieves Bitfinex leveraged long position data and interprets it as large investor bullish sentiment. This distinguishes it from siblings like get_sentiment_indicator or get_contract_oi_data by specifying source (Bitfinex) and metric (long positions).

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?

Description implies usage for sentiment analysis but does not explicitly state when to use this tool versus alternatives (e.g., get_sentiment_indicator, get_contract_oi_data). No guidance on prerequisites or when not to use.

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