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

Annotations already declare the safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false), so the bar is lower. The description usefully adds the 30-symbol cap and per-member ownership scope, but says nothing about duplicate handling, error behavior when the cap is exceeded, or why the operation is non-idempotent as the annotation claims.

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?

A single sentence that front-loads the operation, then the resource, examples, and limit. No filler, nothing to trim.

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?

For a one-parameter add tool with no output schema, the description covers the action, the target, accepted value shape, and the hard limit. Only marginal gaps remain: duplicate behavior and what happens at/over the 30 limit.

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 0%, so the schema only conveys that 'symbols' is a string array. The description compensates by defining what a symbol is (a market ticker), giving concrete examples, and stating the 30-item ceiling that the schema does not encode.

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 ('Adds') plus resource ('markets ... to this member's own watchlist') and scopes it with examples (BTC, WLFI, AAPL). The verb contrast with remove_from_watchlist and get_watchlist makes it unambiguous which operation this is without opening any 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?

The description implies its context (curating one's own watchlist) and supplies a real usage constraint ('up to 30'), but names no alternatives and gives no explicit when/when-not guidance relative to get_watchlist or remove_from_watchlist.

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