nt_chart_reload

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

With no annotations, the description supplies the safety/behavior context. It discloses the local-mode limitation and the F5 analogy, but does not mention potential side effects like resetting indicator states or losing unsaved chart settings.

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 extremely concise, delivering purpose, usage, and mode constraint in a single sentence without any 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 simple tool with one optional parameter and no output schema, the description covers the essential context: what it does, when to use it, and its limitation. It could briefly mention side effects, but overall it is adequate.

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 schema already describes the only parameter (chartId) with 100% coverage. The description adds no extra parameter detail, so the baseline score of 3 applies.

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 states a specific action: 'Reload all NinjaScript on a chart (equivalent of pressing F5)'. This clearly identifies the tool's purpose and distinguishes it from sibling chart tools that query state or list 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?

Provides a clear when-to-use context ('Use after changing data series') and a constraint ('Local mode only'). However, it does not explicitly mention alternatives or when-not-to-use, stopping short of a 5.

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