binance_get_api_trading_status

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

Annotations already mark the tool read-only, idempotent, and non-destructive; the description adds the endpoint, SIGNED/auth requirement, IP weight, the abuse-prevention lock cooldown context, and the -2015 error meaning. This is exactly the kind of behavioral context that annotations do not provide, and it does not contradict them.

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 organized into clear labeled sections (purpose, when to use, when not to use, returns, examples, error handling) with no filler. Every sentence adds operational value, and the main purpose is front-loaded.

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?

The description covers selection criteria, exact endpoint, authentication/error behavior, return format options, and example invocation. For a single-parameter read-only status tool, nothing needed for correct invocation is missing.

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 (response_format), and the description demonstrates an empty params object plus the json override, while the schema supplies the enum/default details. Given the near-zero schema coverage signal, the description compensates well enough for the single optional parameter.

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 first sentence gives a specific verb and resource: 'Report whether spot trading is locked and what triggered it.' It is further distinguished from sibling tools by naming binance_get_account_status and binance_get_api_restrictions as different checks, so an agent can select it correctly.

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 'When to Use' section states a concrete trigger condition (order placement failing for no filter/balance reason) and the 'When NOT to Use' section explicitly names the alternatives for general account status and key permission flags. This leaves no ambiguity about when this tool should be chosen over siblings.

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