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

Annotations already declare readOnlyHint=true and openWorldHint=true. The description adds meaningful behavioral context beyond this: it reveals the funding rate is the native premiumIndex (source of truth), includes basis calculation, and highlights that the index price is a weighted average of multiple exchanges, which could be noisy for small/new pairs. This enriches the agent's understanding without contradicting 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?

The description is dense but every sentence adds value: it specifies the data source, the basis, contrarian interpretation, a caveat about noisy index, and default thresholds. It is front-loaded with the core purpose, though the mixed Indonesian-English phrasing and length could be slightly tighter.

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 the tool's simplicity (one required parameter) and the absence of an output schema, the description covers key operational details: the native source, basis, interpretation guidance, threshold defaults, and a related configuration tool. It does not describe the exact return structure, but for a single-symbol data fetch this is not a significant gap.

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?

There is only one parameter (symbol), and the input schema already provides full coverage (description, pattern, example, and condition that it must be a Binance USDS-M perpetual pair). The tool description itself does not add any further parameter meaning, so the baseline of 3 is appropriate.

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 fetches the current funding rate (native premiumIndex, source of truth) along with basis (mark vs index price). The verb 'Ambil' (get) and the resource are explicit, and the 'TERKINI' (latest) qualifier differentiates it from historical funding rate tools, though it does not name a sibling explicitly.

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 context on when to interpret the data (e.g., contrarian signals for crowded longs/shorts) and warns about noise for small/new pairs, but it does not explicitly state when to use this tool versus alternatives like the funding rate history tool. It mentions a related configuration tool (binance_set_pair_threshold) but no direct alternatives or exclusions.

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