Get official TradingView OHLCV history

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

Annotations provide basic flags (openWorld, not read-only), but the description adds valuable behavior: the browser closes unless keepBrowserOpen is true, CSV is archived locally, default return is a compact summary, and no account upgrade is attempted. This exceeds the annotation-only information without contradicting them.

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 tight paragraph with no filler. Each sentence contributes: main action, includeBars note, browser keep-alive, interval support, and a non-goal. Front-loaded with the key purpose.

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?

Given 8 parameters, no output schema, and annotations present, the description covers the default return format, raw bar inclusion, browser lifecycle, and interval scope. It does not mention rate limits or error cases, but it is sufficiently complete for selection and invocation.

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?

Schema description coverage is high (88%), so baseline is 3. The description adds extra meaning for includeBars ('only when raw OHLCV must enter model context') and keepBrowserOpen (browser lifetime), enriching the parameter understanding 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 the tool opens a TradingView symbol/interval, exports chart data via Supercharts, archives the CSV, and returns a compact summary by default. This distinguishes it from siblings like tradingview_get_day or market_get_quotes by explicitly covering multiple intervals and the archival/export behavior.

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 practical guidance: 'Set includeBars only when raw OHLCV must enter model context' and clarifies browser lifetime with keepBrowserOpen. It does not explicitly name alternative tools, but the context signals and sibling names make the role clear, and the guidance is actionable.

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