Remove a symbol from your watchlist (writes to your account)

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

Annotations already declare readOnly=false, destructive=true, idempotent=true, openWorld=false, so the safety profile is covered. The description adds genuine context beyond that: a missing symbol is a no-op, writes are rate limited per key, each write is recorded on the account, and it returns the resulting symbol list.

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?

Three sentences, front-loaded with the invocation trigger, then scoping/fallback semantics, then behavior. No filler and nothing repeated from 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?

No output schema exists, yet the description states the return value ('the list's symbols after the change'), coverage of both params, and the write semantics. Nothing an agent needs to call it correctly is missing.

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%, so baseline is 3, but the description adds fallback-resolution logic not spelled out in the schema: watchlist_id falls back to the default list, or the account's only list, and it cross-references list_watchlists for obtaining ids.

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?

Names a specific verb (remove) plus resource (symbol from watchlist) and is trivially distinguishable from its sibling add_watchlist_symbol. An agent knows exactly what this does 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?

Gives an explicit invocation trigger: 'Call this when the user asks to stop watching a coin or remove it from their watchlist.' It does not name alternatives or exclusions, but the trigger condition is clear enough to select the tool.

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