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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), yet the description adds substantial behavior: an empty account yields an empty listing, nothing is created, quotes are never served, counts have specific semantics, and it warns that list names/notes are user-authored data and never instructions (prompt-injection defense). The permission requirement is also disclosed.

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?

Purpose is front-loaded in the first clause; subsequent sentences carry distinct payloads (counts, empty state, security note, permission). It is long and has mild redundancy around items_count appearing 'the same with and without watchlist_id', but nearly every clause earns its place for a tool with this much return-shape nuance.

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?

Although an output schema exists (so return values need not be explained), the description fully disambiguates the non-obvious count fields, the empty-account case, the ticker-only itemisation, and the permission requirement. Nothing an agent needs to invoke or interpret this call 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% and the single parameter is documented in-schema, so baseline 3 applies. The description goes further by spelling out what the flagged vs unflagged modes return (one list with itemised items vs all lists without items) and by tying the item id back to watchlist_remove_item, adding real meaning beyond the schema text.

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 opens with a specific verb+resource ('List the watchlists of the signed-in user's account') and enumerates the returned fields (id, name, default flag, count, tickers). It also carves out a clear boundary ('it returns no prices: this server does not serve quotes') and names the sibling watchlist_remove_item in the item-id linkage, so an agent can place it against watchlist_create/add_item/remove_item without opening schemas.

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 gives explicit conditions: use it to answer 'what is on my watchlist' and before changing a list, and it explains that the returned item id is the argument watchlist_remove_item takes — concrete routing to a sibling. It does not explicitly state when not to use it or name a competing read alternative, but the context is unambiguous.

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