okx_get_eth_staking_balance

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

No annotations are provided, so the description must convey behavioral traits. It indicates read-only via '[L:READ]', but fails to disclose whether authentication is needed, side effects, rate limits, or data scope. Minimal transparency.

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 very short but under-specified. It is concise but not well-structured; the instruction to call agent_catalog is unclear. Could be improved without adding length.

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 no parameters and no output schema, the description should at least state what the tool returns or its purpose clearly. It does not, leaving the agent to guess. Not complete enough for a zero-param tool.

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 has zero parameters, so the description does not need to add parameter information. Baseline is 4 for 0-param tools, and the description does not contradict or add confusion.

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 is vague and does not explicitly state that it retrieves ETH staking balance. It uses coded tags like '[L:READ]' and 'CAT:[金融]' but no clear verb+resource statement. The name provides some clue but the description itself is insufficient.

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 includes an instruction to call agent_catalog first, implying a prerequisite, but does not provide any guidance on when to use this tool vs alternatives like okx_get_eth_staking_history or other staking tools. No explicit exclusions or comparisons.

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