BinanceSubAccountGetApiKeyIpRestriction

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

No annotations are provided, so the description carries the full behavioral burden, yet it discloses only that this is a read. It says nothing about required permissions, whether the master account key is needed, or what the restriction payload looks like. For a security-sensitive sub-account tool with zero annotation coverage this is a substantial gap.

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, which is efficient. It is arguably terse to the point of under-specification for a security-related tool, keeping it from a 5.

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 only three fully documented parameters and no output schema, the schema handles most of the load, so the description is close to adequate. However, it never explains what the returned IP restriction comprises or what auth context is expected, leaving a real gap for an agent planning the call.

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 subAccountId, subAccountApiKey and recvWindow each documented in the schema, so the baseline of 3 applies. The description adds no meaning beyond the schema, such as the significance of the recvWindow cap.

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?

States a specific verb and resource ('Get IP restriction for a sub-account API key'), which unambiguously identifies the read-side counterpart to the sibling BinanceSubAccountUpdateIpRestriction. It does not explicitly name that sibling as the alternative, so it stops short of a 5.

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 guidance on when to use this versus BinanceSubAccountUpdateIpRestriction or the other sub-account API-key tools, and no stated prerequisites (e.g. that it likely requires a master-account key and the sub-account's API key). The agent must infer usage from the name alone.

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