nt_accounts

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 clearly indicates a read-only list operation and specifies the included data (balances and open position counts). However, it does not disclose potential performance implications, scope boundaries (e.g., demo vs live), or error behavior. The verb 'list' implies no side effects, but this remains implicit.

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 a single, well-structured sentence that front-loads the action and resource, with no wasted words.

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 zero-parameter list operation, the description adequately covers the purpose and expected output content (balances and open position counts). There is no output schema, but the description states what is returned. It could be considered complete, though details on response format are omitted.

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, so the description adds no parameter semantics. Under the rubric, the baseline for 0 parameters is 4; the description is clear that no input is required.

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 uses the specific verb 'List' and identifies the resource as 'all trading accounts in NinjaTrader', specifying the return fields (balances and open position counts). This clearly distinguishes it from sibling tools like nt_account_info or nt_account_balance, which target a single account.

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 for retrieving a high-level view of all accounts, but it does not explicitly state when to choose this over nt_account_info, nt_account_balance, or nt_positions, nor does it mention any exclusions or alternatives. The usage guidance is only implicit.

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