BinanceNewUserDataStream

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the creation purpose but doesn't mention what the tool returns (e.g., a listenKey), that the stream expires, or that it requires authentication. These are important behavioral traits for a create operation, so the description is insufficient.

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 a single, well-structured sentence with no filler. It front-loads the verb 'Create' and conveys the essential information in 14 words, with every word earning its place.

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 lacks important operational context. With no output schema, it should explain that the tool likely returns a listenKey needed for WebSocket connection, and that the stream must be maintained via PutUserDataStream and closed with DeleteUserDataStream. The absence of these details makes the tool incomplete for an agent to use correctly.

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?

The input schema has zero parameters, so the schema description coverage is 100%. Per the guidelines, a zero-parameter tool gets a baseline of 4. The description doesn't need to explain parameter details since none exist.

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 action (create), the resource (new user data stream), and the purpose (receive account updates via WebSocket). This distinguishes it from sibling tools like BinanceDeleteUserDataStream and BinancePutUserDataStream, which handle deletion and keepalive respectively.

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?

No guidance is provided on when to use this tool versus alternatives. It doesn't mention that this is the first step in the stream lifecycle, nor does it reference the need for PutUserDataStream to keep the stream alive or DeleteUserDataStream to close it. The description leaves the usage context entirely implicit.

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