get_account_info

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

No annotations are provided, so the description carries the full burden. It does disclose the return payload (balance, equity, margin, free margin, margin level, leverage), which is meaningful given there is no output schema, but it says nothing about read-only nature, latency, units/currency of the values, or what happens if no account is connected.

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?

It is a single terse sentence fragment with zero waste, appropriately sized for a zero-argument snapshot tool. It is front-loaded with the most important field (balance), though the absence of any verb phrase slightly weakens the lead.

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?

For a trivial zero-parameter read, the main missing piece is the return-value framing, and without an output schema the field enumeration does useful work there. However, it omits units, whether margin level is a ratio or percentage, and any condition under which the call fails or returns empty, so it is only minimally complete.

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 tool takes zero parameters, so per the rubric the baseline is 4. There is no argument surface to document, and the description does not need to compensate for anything here.

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 enumerates the data the tool exposes (balance, equity, margin, free margin, margin level, leverage), which makes the resource identifiable, but it is a bare noun phrase with no verb and no differentiation from siblings like get_terminal_info or get_positions. An agent can infer it returns account state, but the purpose is stated as a field list rather than an action.

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?

There is no when-to-use guidance at all. Nothing tells the agent when to call this instead of get_terminal_info for account-adjacent data, nor whether it is a snapshot or requires a prior login/connection. The field list implies usage but does not state it.

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