BinanceSubAccountGetFuturesSummary

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

No annotations are supplied, so the description carries the full disclosure burden, yet it only implies read-only behavior through the word "Query." It says nothing about required API key permissions (master-account key for sub-account endpoints), rate limits, or what happens when the optional email is omitted (aggregate across all sub-accounts vs. error).

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?

A single front-loaded sentence with no filler or redundancy. Its brevity is efficient, though it borders on under-specification for a tool with cross-account behavior.

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?

With no annotations and no output schema, the description is the only source of behavioral context, and it does not describe the fields a futures summary returns or the cross-sub-account semantics. It is minimally adequate for a low-risk read endpoint but leaves real gaps for an agent deciding how to call it.

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%, so both parameters (email, recvWindow) are already documented in the schema, which sets the baseline at 3. The description adds no meaning beyond that — notably it does not clarify the aggregation behavior when email is left out.

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 pairs a specific verb ("Query") with a specific resource ("sub-account futures account summary"), which lets an agent distinguish it from BinanceSubAccountGetSpotSummary or BinanceSubAccountGetMarginSummary by asset class. It stops short of naming those siblings or stating scope (single sub-account vs. all), so it is clear but not fully differentiating.

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?

There is no when-to-use guidance, no exclusions, and no mention of the closely related BinanceSubAccountGetFuturesPositionRisk or the spot/margin summary siblings. The agent must infer on its own that this returns aggregate futures balances rather than position-level detail.

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