tv_auth_session_set

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only says 'persist' and does not disclose whether the call overwrites an existing session, validates inputs, or has side effects such as clearing previous auth state.

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?

A single sentence with an active verb and no filler. The core message is front-loaded and every word earns its place.

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 no annotations, no output schema, and four undocumented parameters, the description is too sparse for an agent to invoke correctly without additional external knowledge. It does not clarify parameter relationships, defaults, or expected outcomes.

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 the undocumented parameters. It only generically maps to 'cookie' and leaves source, sessionid, and sessionid_sign entirely unexplained, leaving the agent uncertain about what values to pass.

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 names the action (persist), the resource (TradingView session cookie), and the audience (authenticated tv_auth_* tools), which distinguishes it from siblings like tv_auth_session_start or tv_auth_session_clear. It is clear about the core operation, though it does not enumerate the exact session fields being stored.

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?

No guidance on when to choose this tool over the many tv_auth_* siblings such as tv_auth_session_start, tv_auth_session_status, or tv_auth_session_clear. The description implies a persistence use case but does not state prerequisites, ordering, or alternatives.

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