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

The annotations already include destructiveHint=true, but the description adds context that removal 'only stops tracking and can be undone with add_to_watchlist,' clarifying that it is not an irreversible deletion. This goes beyond the annotation by explaining the scope and reversibility, though it doesn't describe other potential side effects.

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 two sentences long, front-loaded with the main purpose, and every sentence adds value: the first states the action, the second provides usage constraints and reversibility. No redundancy or irrelevant detail.

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 tool's simplicity (one parameter), the presence of an output schema, and annotations covering destructive behavior and idempotency, the description provides sufficient context for a correct invocation. It covers the key decision points: when to call and what the effect is.

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 description coverage is 100%, so the parameter 'tickers' is already fully documented with an example in the schema. The description does not add new semantic detail beyond what the schema provides, so the baseline of 3 applies.

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 tickers from the user's saved watchlist.' It uses a specific verb and resource, and the distinction from the sibling add_to_watchlist is implicit in the action itself. The tool's scope is well-defined.

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 explicitly instructs when to use the tool: 'Only call this when the user explicitly asks to stop tracking, remove, or drop a ticker.' It also gives a clear exclusion: 'never prune the watchlist on your own initiative,' and mentions undoing via add_to_watchlist, which guides agent decision-making.

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