nt_chart_list

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

With no annotations, the description carries the transparency burden. It discloses the 'Local mode only' restriction and clarifies that it lists all open charts, implying a read-only operation. However, it does not mention failure modes, prerequisites (e.g., NinjaTrader running), or whether the result is a simple list or a structured payload.

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, clear sentence followed by a brief constraint. It is front-loaded with the action and output fields, with no filler words or redundant schema information.

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 list tool with no params and no output schema, the description adequately covers what it does, what it returns (symbol, timeframe, chart ID), and the local-only limitation. Minor gaps remain about error behavior and return format, but these are not critical for a straightforward enumeration tool.

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 has zero parameters, so schema coverage is trivially 100%. Per rubric, a tool with 0 params gets a baseline of 4. The description adds no parameter details because none exist; thus it cannot add more meaning beyond the schema.

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 'List all open chart windows in NinjaTrader' with specific outputs (symbol, timeframe, chart ID). This distinguishes it from sibling tools like nt_chart_state or nt_chart_instrument, which target individual charts rather than enumerating all open windows.

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: call this when you need to see all open charts. However, it does not explicitly contrast it with alternatives or mention when not to use it. The 'Local mode only' constraint is a limitation but not a comparison.

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