BinanceDeleteUserDataStream

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

With no annotations provided, the description carries the full burden. It discloses the core behavior (invalidating the listen key) but does not state consequences such as the stream no longer delivering updates or whether the action is irreversible. For a delete-like operation, this is minimal but not misleading.

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 clear sentence with no wasted words. It is front-loaded with the action and resource, making it easy to parse.

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?

For a simple one-parameter delete stream tool with no output schema, the description covers the essential behavior. It could mention the relationship to the other user data stream tools, but it is adequately complete for the operation's simplicity.

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% for the single parameter 'listenKey'. The description adds the context 'by invalidating the listen key' but this essentially restates the schema's 'Listen key to close' without providing new meaning, so it stays at baseline 3.

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 uses a specific verb 'Close' and clearly identifies the resource 'user data stream' with the mechanism 'by invalidating the listen key'. This distinguishes it from siblings like BinanceNewUserDataStream (create) and BinancePutUserDataStream (keep-alive).

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 usage is implied by the action 'Close' but there is no explicit when-to-use guidance or mention of alternatives. It does not state 'use this when you no longer need updates' or compare with BinancePutUserDataStream, so the guidance is not fully fleshed out.

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