BinanceGetAccount

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

With no annotations provided, the description must disclose behavior. 'Get' implies a read operation, but the description does not state what data is returned, whether authentication is required, or if there are any side effects. Given the many similar account tools, this lack of detail means the agent cannot infer the tool's exact scope or safety profile.

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, concise sentence with no filler. It is front-loaded with the action verb 'Get' and the resource 'current account information'. While minimal, it is appropriately sized for a simple read operation, though it could include more specificity without becoming verbose.

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?

Given the large number of account-related sibling tools (BinanceWalletAccountInfo, BinanceWalletAccountStatus, BinanceWalletBalance, etc.) and the absence of an output schema or annotations, the description is insufficiently complete. It does not clarify what 'account information' encompasses or how this endpoint differs from similar ones, leaving the agent without enough context to invoke it 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?

Schema coverage is 100% because the only parameter recvWindow has a description ('The value cannot be greater than 60000'). The tool description itself adds no additional parameter context, but the schema already documents it sufficiently. Baseline of 3 applies.

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 'Get current account information' uses a clear verb and resource, making it understandable. However, it does not distinguish from sibling tools like BinanceWalletAccountInfo or BinanceWalletAccountStatus, which may also return account-related details. The term 'current account' is not explicitly scoped to spot trading, leaving ambiguity.

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 provides no guidance on when to use this tool versus alternatives. It does not mention whether this is the primary account endpoint for spot trading or how it relates to other account-related tools in the sibling list. No exclusions or prerequisites are stated.

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