binance_get_earn_account

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint false. The description adds value by disclosing the SIGNED/USER_DATA requirement, the 150 IP weight, the return format options, and specific error semantics (-2015 and all-zero amounts). No contradiction with annotations.

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?

Well-organized with clear sections (Summary, API call, When to Use, When NOT to Use, Returns, Examples, Error Handling). Every sentence serves a purpose, and the critical summary is front-loaded. No wasted words.

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?

Covers the tool's purpose, usage context, return format, examples, and error handling. Given the output schema exists and the tool is a read-only snapshot, the description provides all necessary information for an agent to call it correctly without referencing additional docs.

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 0%, but the description compensates somewhat with examples (params = {}, params = {"response_format": "json"}) and a mention of response_format in the Returns section. However, the schema already documents response_format with a clear description, so the description adds only marginal clarification beyond what the schema provides.

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 opens with a specific verb and resource: 'Summarize total Simple Earn holdings (Flexible + Locked) in BTC and USDT.' It also names the underlying endpoint and explicitly distinguishes itself from sibling position tools, making its scope unambiguous.

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?

Includes dedicated 'When to Use' and 'When NOT to Use' sections. It tells the agent exactly when a one-call snapshot is appropriate and points to the two sibling tools for individual positions, leaving no ambiguity about selection.

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