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

No annotations are provided, so the description carries the full behavioral burden. It does not state whether this is a read-only operation, whether it requires an authorized trading key or scope, whether live balances trigger real network calls, or whether sensitive fields (deposit address, scopes) are redacted in paper mode — all material for a credentials-adjacent account tool.

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?

A single front-loaded line listing exactly what comes back, with the paper|live enum inlined usefully. It is terse to the point of being a field dump rather than prose, but nothing is wasted.

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 annotations and no output schema, the description must convey what comes back and what the call entails; the field list does the former adequately but leaves the behavioral and authorization picture entirely unstated. For an account-introspection tool on a trading platform, the missing safety and permission context is a real gap.

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?

There are zero parameters, so the baseline is 4 and the description adds nothing that could mislead. Minor deduction avoided since calling requires no arguments, though the description could have noted that it takes none.

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 names the specific resource (agent account) and enumerates the returned fields: status, mode (paper|live), scopes, live balances, deposit address, limits. That is concrete and distinguishable from siblings like get_limits, get_trading_wallet, or get_positions, though it overlaps somewhat with those dedicated tools without saying how they relate.

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 implies usage as the general-purpose account snapshot, but gives no explicit when-to-use guidance and never mentions the overlapping siblings (get_limits, get_trading_wallet, guardian_status, get_metrics) or when to prefer those instead. Usage is inferable rather than stated.

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