Remove Stocks from Watchlist

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

Annotations already disclose destructiveHint=true, readOnlyHint=false, and idempotentHint=true. The description adds little behavioral context beyond the obvious fact that symbols are removed, so it does not carry much extra burden.

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 compact and front-loaded with the core action, followed by two relevant use-case bullets. There is no filler or redundant restatement of structured fields.

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 simple one-parameter mutating tool, the description covers the action, the single-removal case, and the clear-all workflow requiring get_watchlist. Combined with the schema and annotations, nothing essential is missing for an agent to call it correctly.

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%, and the schema already documents the symbols array with examples. The description reinforces the example use cases but does not add meaningful parameter semantics beyond the schema.

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 'Remove one or more stocks from the user's watchlist,' which states a specific verb, resource, and scope. This clearly distinguishes it from siblings like add_to_watchlist, get_watchlist, and remove_portfolio_stocks.

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 use cases provide concrete trigger phrases for single removal ('Stop watching INFY') and full clearing ('Clear my watchlist'). It also gives the necessary prerequisite for clearing all symbols: get watchlist first. It does not explicitly name alternatives or when not to use this tool, but the context is clear.

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