watchlist_remove_bulk

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

With no annotations, the description carries the full burden. It discloses a non-obvious behavioral trait: removal is sequential. It also states that per-symbol results are reported, which hints at possibly partial success. This goes beyond the schema and name, though it could elaborate on failure handling or what happens when a symbol is missing.

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 sentence that is front-loaded with the action ('Remove multiple symbols'), contains zero filler, and conveys the key facts: multiple, sequential, and per-symbol reporting. It is concise and well-structured.

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 the low complexity (one array parameter, no output schema), the description adequately covers the essential operation and its behavioral nuances (sequential, per-symbol results). It does not need to detail return format or edge cases, though a mention of the 100-item limit could slightly enhance completeness.

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 coverage is 100%: the only parameter 'symbols' has a description 'Symbols to remove'. The tool description adds context about sequential processing and per-symbol results, but does not add significant semantic detail beyond what the schema already provides for the parameter itself.

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 uses a specific verb 'Remove' with a clear resource ('multiple symbols') and differentiates from sibling watchlist_remove by emphasizing bulk and sequential processing. It also adds 'report per-symbol results', which uniquely describes this tool's scope.

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 'multiple symbols' and the tool name 'watchlist_remove_bulk' clearly imply this is for batch removal, contrasting with the singular sibling watchlist_remove. However, it does not explicitly state 'use this instead of watchlist_remove when removing more than one symbol' or mention any exclusions, so it misses the explicit alternative guidance.

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