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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=true, and openWorldHint=false, so the safety profile is covered. The description adds real context on top: the permission requirement, ambiguity handling for duplicate tickers, and an explicit non-effect statement about portfolios and broker accounts. Return-value behavior is left to the output schema, which exists.

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 short sentences, front-loaded with the action and resource, each carrying distinct information (scope, permission prerequisite, ambiguity rule, non-effect). No filler or restatement of the title.

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 four-parameter mutation tool this is close but incomplete: the permission gate and exchange rule are covered, and the output schema handles return values, yet the targeting semantics of watchlist_id (arguably the most important decision for a tool with multiple watchlist siblings) are absent.

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?

At 0% schema description coverage the description must carry parameter meaning, and it only partly does. It gives genuinely useful semantics for 'exchange' (supply it when multiple active listings share a ticker) and implies 'ticker' must be a valid listed security, but 'watchlist_id' and 'operation_id' are never mentioned — an agent cannot tell which watchlist is targeted by default or what the operation_id is for.

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 names a specific verb and resource ('Add one verified stock or ETF to my ValuEdge Watchlist') and states the cardinality constraint (one security at a time). This clearly separates it from create_my_watchlist, remove_from_my_watchlist, and the portfolio-mutation siblings, though it never names a sibling explicitly.

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 a concrete precondition (explicit per-client Watchlist write permission granted in ValuEdge) and a conditional routing rule: if multiple active listings share a ticker, request the exchange. It also carves out what it will not do ('Never modifies a portfolio or broker account'), which steers away from the portfolio tools. It stops short of naming alternatives for related operations.

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