remove_watchlist

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

The description states 'remove', which is consistent with the annotations (destructiveHint: true, readOnlyHint: false). It does not add extra behavioral details beyond the annotations, such as side effects or error handling.

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 highly concise and front-loaded with the core action. Every word is necessary and no fluff.

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 simplicity of the tool (removal, no output schema), the description is reasonably complete. It covers the main function and parameter usage, though it omits post-removal behavior or error cases.

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?

The description adds value beyond the schema by clarifying the mutual exclusivity of the id and stockId+market parameters. The schema has 33% coverage (only id described), and the description compensates by explaining the two modes of identification.

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 clearly states the action 'remove', the resource 'a stock from the watchlist', and how to identify the stock (by id or stockId+market combination). It effectively distinguishes from sibling tools like add_watchlist or update_watchlist.

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 indicates when to use: to remove a stock from the watchlist. However, it does not provide any guidance on prerequisites, what happens if the stock is not found, or when not to use it. It is adequate but minimal.

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