BinanceWalletAssetDividendRecord

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

No behavioral traits beyond the basic 'get' action are disclosed. With no annotations provided, the description carries full responsibility, but it doesn't explain if this returns a list, paginates, requires specific time ranges, or any other behavior.

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 with no redundant words, but it is under-specified to the point of providing minimal value. It is concise but not substantial enough to be considered effective.

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?

With no output schema and no annotations, the description is the only source of context beyond the parameter list. A one-sentence description fails to explain the tool's role, return format, or edge cases, making it inadequate for a tool with 5 optional parameters.

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 input schema provides descriptions for all 5 parameters, giving the agent full parameter-level information. Since the description itself adds no parameter semantics, the baseline score 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 uses the verb 'Get' with the resource 'asset dividend record', clearly indicating a retrieval operation. However, it does not distinguish this from related siblings like BinanceEarningsList or BinanceWalletAssetDetail, and it is ambiguous whether 'record' is singular or plural.

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 instead of alternatives. It lacks any mention of prerequisites, intended use cases, or distinctions from similar wallet/financial data tools.

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