watchlist_add

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

No annotations are provided to indicate safety or side effects (e.g., readOnlyHint, destructiveHint). The description only mentions 'Add,' implying mutation, but it does not disclose what happens if the symbol already exists, whether the operation is idempotent, or what the response contains. This lack of behavioral detail burdens the agent to explore behaviorally.

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?

The description is succinct, consisting of two sentences that immediately convey the primary action and a secondary feature. Every word is relevant, and there is no redundancy or filler. It is appropriately front-loaded with the core purpose.

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?

Given the moderate complexity (3 parameters, 2 required) and the presence of an output schema (which could document return values but is not shown), the description is incomplete. It fails to explain how to obtain a valid watchlist_id, error handling (e.g., duplicate symbol), or what the tool returns. A more complete description would address these gaps.

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 input schema has 0% description coverage, so the description must compensate. It mentions 'existing watchlist' (implying watchlist_id), 'ticker symbol' (symbol), and 'optional notes' (notes), but it does not explain what these parameters mean in context (e.g., where to find watchlist_id, symbol format, or how notes are used). The description adds minimal value beyond the schema.

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 clearly states the tool's purpose: 'Add a ticker symbol to an existing watchlist.' It uses a specific verb ('Add') and resource ('ticker symbol to an existing watchlist'), and the optional notes detail further clarifies the function. Sibling tools like watchlist_create and watchlist_remove help differentiate this tool from related operations.

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 usage when adding a symbol to an existing watchlist, but it does not provide explicit guidance on when to use this tool versus alternatives (e.g., watchlist_create for creating a new watchlist, or add_portfolio_position for adding to a portfolio). There is no mention of prerequisites or exclusions, leaving the agent to infer context.

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