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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered. The description adds real value beyond that: the auth scope requirement and a specification of the returned element formats (BTC, PURR/USDC, xyz:TSLA, @107), which is important given there is no output schema.

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?

One dense sentence plus a routing clause and an auth note — every part earns its place and the core identification is front-loaded. The nested parenthetical '(the watchlist the trade page's star toggles keep)' is slightly convoluted but still readable in one pass.

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, the description correctly compensates by describing the shape of each returned symbol and naming the auth scope. It doesn't say what happens when the watchlist is empty or whether ordering is guaranteed, but nothing essential to calling 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?

The tool takes no parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The parenthetical detail about market-id forms is aimed at interpreting results rather than inputs, which is appropriate here.

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?

States a specific verb+resource ('YOUR starred symbols… the watchlist') and pins down exactly what each entry is: a canonical market id in one of four documented forms (perp ticker, spot pair, HIP-3 symbol, spot index). It also names the sibling that mutates it ('Change it with update_watchlist'), so an agent can tell this apart from update_watchlist without opening either 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?

Explicitly routes mutation intent to update_watchlist and states the required scope ('Requires api:read.'), which is the main precondition for calling it. It doesn't state an explicit negative case (e.g. when to prefer get_tracking_updates), but for an unambiguous read of a personal list that is a minor gap.

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