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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so the safety profile is covered structurally. The description's added value is the non-obvious multi-step bulk-removal procedure, though it never states that removal is permanent or what happens for symbols not on the watchlist.

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?

Opens with the core action in one sentence, then uses a compact bulleted use-case block. Every line carries distinct information and nothing repeats the title or schema.

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 destructive mutation with no output schema, the description supplies the operationally critical bulk-removal recipe that is missing from schema and annotations. It stops short of stating error behavior for unknown symbols or explicitly confirming permanence, which would make this fully complete.

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% and the single parameter is fully documented with an example (['INFY', 'TCS']) plus min/max item constraints. The description's 'one or more' adds only cardinality, which the schema already encodes via minItems/maxItems, so baseline 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?

States a specific verb (remove) and resource (stocks from the user's watchlist), and the phrasing 'one or more' matches the array parameter's cardinality. It is cleanly distinguishable from add_to_watchlist, get_watchlist, and remove_portfolio_stocks in the sibling list.

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?

Provides two concrete use cases with the natural-language triggers ('Stop watching INFY', 'Clear my watchlist') and, for the bulk case, an explicit prerequisite workflow: call get_watchlist, page with next_offset until has_more is false, then remove. That is when-to-use and how-to-use guidance an agent would otherwise have to guess.

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