BinanceWalletBrokerWithdraw

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

No annotations are provided, so the description carries the full burden. It only mentions 'initiate' and 'travel rule compliance' without disclosing the mutating nature, consequences (e.g., irreversible fund transfer), required permissions, or return value. This is a significant gap for a withdrawal tool.

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, front-loaded sentence that captures the core action and differentiator. It wastes no words and is appropriately sized for the information it conveys.

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?

Despite having 12 parameters, 8 required, and no output schema, the description is minimal. It does not explain what the tool returns, the compliance workflow, or how it relates to sibling withdrawal tools. The high complexity and lack of annotations demand more context than this one-liner provides.

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 schema covers all 12 parameters with descriptions, so the baseline is 3. The tool description adds no extra semantic meaning beyond the schema; it references 'broker withdrawal' but does not explain how parameters like subAccountId or originatorPii relate to the broker context.

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 ('Initiate') and resource ('broker withdrawal') and adds a distinguishing qualifier ('with travel rule compliance'). This clearly differentiates the tool from sibling tools like BinanceWalletWithdraw and BinanceWalletWithdrawTravelRule by scoping it to broker withdrawals.

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 is for broker withdrawals, which provides clear context for when to use it. However, it does not explicitly state when not to use it or name alternative tools, so it lacks explicit exclusions.

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