get_dual_balances

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

The description does not disclose behavioral traits such as read-only nature, side effects, or what kind of data is returned. It only states what the data represents, not how the tool behaves.

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 concise and to the point, containing no unnecessary words. It is a noun phrase rather than a sentence, but it is still clear enough for the purpose.

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?

The description lacks context about what 'dual-investment' means, what the returned balances look like, and when this tool is appropriate. Given the many sibling tools with similar get operations, this description is too minimal to guide an agent effectively.

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 is empty, so there are no parameters to describe. The description does not explain that the tool takes no arguments, but since there are none, this is not a major gap. A more explicit statement could clarify that it returns all balances without filtering.

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 a noun phrase stating the account's dual-investment balances, but it lacks an explicit action verb like 'get' or 'fetch'. The tool name implies the action, but the description could be more explicit about what it does.

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?

No guidance is provided on when to use this tool versus other get tools (e.g., get_balances, get_dual_prices). The description does not mention any distinguishing use case or conditions.

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