BinancePutUserDataStream

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

With no annotations, the description carries the full burden for disclosing behavioral details. It only restates the tool's purpose without mentioning side effects, prerequisites, rate limits, or what happens if the key is expired. This is a minimal restatement of the tool's name and offers no additional transparency.

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 sentence that is direct and unambiguous. Every word earns its place, with no unnecessary filler or repetition.

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?

This is a simple tool with one parameter and no output schema, so a large description is not required. The description conveys the essential action clearly. However, it leaves out potentially useful context such as the need to call this periodically before the listen key expires, but given the simplicity, it is nearly complete.

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 coverage is 100% (the parameter has a description). The description adds little beyond the schema: 'Extend the validity' clarifies that the listenKey is the one being kept alive, but it does not provide richer semantics like format, length, or example values. Baseline of 3 is appropriate.

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 ('Extend') and clearly identifies the resource ('user data stream listen key'), distinguishing it from sibling tools like BinanceNewUserDataStream (create) and BinanceDeleteUserDataStream (delete).

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 description implies the tool should be used to keep a user data stream alive, but it does not explicitly state when to use it relative to alternatives or mention any preconditions (e.g., listen key must already exist). No exclusions or alternative references are provided.

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