watchlist_remove

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

With no annotations, the description carries the burden of disclosing behavior, and it does state the mutating effect and the 'active' scope. It does not disclose whether removal is permanent, how invalid symbols are handled, or any side effects on watchlist 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?

The description is a single concise sentence with the action and target front-loaded. No filler or redundant detail.

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 one-parameter, no-output-schema tool, the description plus well-documented schema gives enough context to select and invoke it correctly. Slight gap is lack of detail on error/confirmation behavior, but this is low-risk for a simple removal operation.

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?

Input schema already covers the only parameter with a clear description of bare vs. full symbol formats, so the description adds little parameter-level meaning. Baseline 3 is appropriate because schema coverage is 100% and no descriptor beyond 'one or more' is needed.

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?

Description states an explicit verb ('Remove') and resource ('one or more symbols from the active TradingView watchlist'), making the action unambiguous. It is clearly distinct from sibling tools like watchlist_add and watchlist_get.

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?

Usage is implied: an agent would call this when it needs to remove symbols from the active watchlist. However, it does not explicitly reference alternatives or state when not to use it, such as when adding symbols or targeting a non-active watchlist.

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