BinanceWalletSubmitDepositQuestionnaire

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

With no annotations, the description carries full burden for behavioral disclosure. It does not mention that this is a write operation, any side effects, authentication requirements, rate limits, or what the response contains. The tool likely submits sensitive compliance data, yet no such context is provided.

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-formed sentence with no redundancy. It is appropriately concise for stating the core purpose, though it lacks any additional structure such as usage notes or parameter context.

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 6-parameter tool with 5 required fields, no output schema, and no annotations. The description is insufficiently complete: it doesn't explain the travel rule context, the purpose of the questionnaire, the role of beneficiaryPii, or what happens after submission. Tool usage would be ambiguous without external knowledge.

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%, but the parameter descriptions are terse (e.g., 'Signature', 'Deposit ID'). The tool description adds no extra meaning about parameter formats, relationships, or how to generate values like the signature. The baseline of 3 applies because the schema does provide basic descriptions for all parameters.

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 (submit) and the resource (deposit questionnaire), and specifies the context (broker deposit). However, it does not differentiate from the sibling tool BinanceWalletSubmitDepositQuestionnaireTravelRule, which appears to be a nearly identical function.

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?

There is no guidance on when to use this tool versus alternatives. No prerequisites, exclusions, or scenarios are described. The single sentence provides no usage context beyond the basic action.

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