get_trading_account

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

With no annotations provided, the description must carry behavioral disclosure. It implies a read-only operation through 'Get' and lists what is returned, which is useful. However, it does not explicitly state that it has no side effects, does not mention authentication or account-selection behavior, and does not clarify whether 'trading account' refers to the default/authenticated account.

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, front-loaded with the action, and uses a tight bullet list for the key returned account details. Every sentence and bullet adds relevant information without padding.

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 simple no-parameter getter with an output schema, the description is largely complete: it names the resource and covers the main account data areas. It is slightly undermined by not noting which account is returned (e.g., the authenticated/default account) and by the absence of any read-only or usage clarification, but these are minor given the tool's simplicity.

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 has zero parameters and the schema is fully covered by an empty properties object, so there is nothing for the description to add. The baseline for a no-parameter tool is 4, and the description appropriately does not invent parameter guidance.

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 clearly states the tool gets trading account information and adds specific detail via bullets (buying power, portfolio value, status, paper-trading flag). It is not a vague tautology, but it does not explicitly distinguish itself from sibling tools like get_trading_config or get_positions.

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 gives no guidance on when to use this tool versus alternatives. It does not mention that it is the right choice for account-level balances/status as opposed to positions, orders, or configuration, nor does it state any exclusions.

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