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

Annotations already flag this as a non-read-only, destructive operation, and the description usefully sharpens that by revealing the full-list wipe that occurs when itemId is omitted — exactly the blast-radius context the annotation alone cannot convey. It stops short of stating irreversibility or the response on a missing itemId, which would push this higher.

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 first sentence is tight and front-loaded with the core behavior. The second sentence, a list of swapchan_playbook workflow names (find-money, best-swap, rebalance, etc.), is irrelevant to invoking this tool and is pure noise for an agent deciding how to call unwatch_token.

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?

With no output schema and only two parameters, the description covers the essential modes of operation and the source of itemId. However, it omits what happens when itemId is not found, whether the watchId list persists after a full clear, and any confirmation of return value, while spending budget on unrelated playbook names.

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 50%, with watchId well documented in the schema but itemId bare. The description compensates by explaining that itemId comes from list_watches and by defining its optionality semantics, which the schema does not state.

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 names a specific verb (remove) and resource (watchlist item or entire watchlist), and explicitly distinguishes the two deletion scopes via the presence or absence of itemId. This is sufficient for an agent to tell it apart from watch_token and list_watches without opening the schema.

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?

It states the two operating modes clearly: pass itemId to remove one item, omit it to clear the entire watchlist, and points to list_watches as the source for itemId. It does not explicitly name watch_token as the counterpart for adding watches, but the usage context is otherwise unambiguous.

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