watchlist_remove

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

Description reveals that this is a write operation (remove/delete), consistent with readOnlyHint=false. It adds behavioral context about the two deletion modes and required parameters, though it could mention what happens if the list does not exist.

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?

Two concise sentences, front-loaded with the main purpose. Every sentence adds value with no redundancy.

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?

The description covers both operational modes and provides usage examples. It is complete for a simple remove tool with two clear use cases, though it could optionally mention error behavior.

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?

Despite low schema coverage (33%), the description adds meaning by explaining how list_type + name identify the list and how items determines whether specific items are removed or the whole list is deleted. This compensates for missing schema descriptions.

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 tool removes items from a tracking list or deletes the entire list, using specific verbs and resource. It distinguishes between two modes (remove items vs delete list) and implicitly differentiates from sibling tools like watchlist_add and watchlist_list.

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?

Explicitly provides when-to-use guidance with example user phrases ('stop tracking...', 'remove from my watchlist', 'delete my list'). Clearly explains parameter usage: provide items to drop specific ones, omit items to delete the entire list.

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