tv_auth_custom_lists

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

The description explicitly indicates that the data is 'authenticated' and sourced from the user's 'TradingView profile session,' implying a prior session is required and that this is a read operation. However, it does not disclose failure modes, rate limits, data freshness, or how the optional filters affect behavior, and no annotations are available to fill that gap.

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, tightly worded sentence with no filler: verb, resource, and source are front-loaded. Every phrase adds meaning, making it easy to parse quickly.

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?

With no output schema and no annotations, the description leaves the return shape and selection semantics undefined. It also lacks usage guidance relative to sibling tools, making this a bare-minimum description that supports a first guess but not confident invocation of the optional parameters.

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%, and the description does not explain 'limit,' 'list_id,' or 'list_name.' The schema offers only type and default bounds, so an agent cannot tell whether list_id and list_name are mutually exclusive, how limit applies, or what 'rows' refers to.

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 opens with the specific verb 'Load' and the resource 'authenticated TradingView custom tracking lists and rows,' with the source 'from your TradingView profile session.' This makes the operation clear and distinguishes it from session-management or symbol-level siblings, though it does not explicitly name any alternative tool.

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 provides no guidance on when to use this tool versus sibling tools like tv_auth_watchlist or other list-related tools. There are no exclusions, prerequisites, or alternative routing cues, so the agent must infer usage from the name alone.

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