tv_auth_symbol_full

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

There are no annotations, so the description carries the full burden. It discloses that this is a read-style fetch and lists what kinds of data are included, which adds useful behavioral context. However, it does not explain whether a prior session login is required, what happens on invalid credentials or missing entitlements, or how the response is structured.

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, front-loaded sentence with a parenthetical list of payload categories. It is compact and avoids filler, though the parenthetical list is slightly dense and could be split for readability.

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 six parameters, no output schema, and no annotations, the description leaves important gaps: it does not explain authentication prerequisites, how parameters relate to the 'authenticated mode', how the returned payload is organized, or what distinguishes this from tv_scrape_symbol_full. The listed content categories are helpful but not sufficient for reliable 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 0%, so the description must compensate for six undocumented parameters. It adds only a weak contextual hint that cookie/sessionid/sessionid_sign relate to 'authenticated mode', and symbol is implied by 'symbol payload'. It provides no meaningful detail about market, exchange, cookie, sessionid, or sessionid_sign semantics beyond their names.

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 ('Fetch rich TradingView symbol payload') and enumerates the payload contents: scanner analytics, technical labels, profile metadata, and entitlement context. It is clear about what the tool returns but does not explicitly contrast it with siblings like tv_scrape_symbol_full or tv_auth_symbol_analytics, leaving some differentiation to inference from the name.

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 phrase 'in authenticated mode' implies this tool should be used when an authenticated TradingView session is available, but the description does not explicitly say when to choose this over tv_scrape_symbol_full, tv_auth_symbol_analytics, or tv_auth_symbol_analytics. Usage context is implied rather than stated with clear conditions or alternatives.

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