add_to_watchlist

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the action ('Adds') but does not reveal critical traits such as whether it requires authentication, if it's idempotent, what happens on duplicate adds, rate limits, or the response format. This leaves significant gaps for a mutation tool.

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 a single, efficient sentence with no wasted words, making it appropriately sized and front-loaded. Every word contributes directly to stating the tool's 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 tool has an output schema (which reduces the need to describe return values) but no annotations and low parameter coverage, the description is minimally complete. It states the basic action but lacks details on behavior, parameters, and usage context, making it adequate only for very simple scenarios.

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 1 parameter with 0% description coverage, and the description does not add any meaning beyond the parameter name 'symbol'. It fails to explain what 'symbol' represents (e.g., ticker format, asset type) or any constraints, which is inadequate given the low schema coverage.

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 states the tool's purpose with a clear verb ('Adds') and resource ('a symbol to the monitoring watchlist'), but it does not differentiate from its sibling tool 'remove_from_watchlist' or specify what type of symbols (e.g., stocks, crypto) or watchlist context (e.g., user-specific, global) it operates on, making it somewhat vague.

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 provides no guidance on when to use this tool versus alternatives like 'remove_from_watchlist' or other monitoring-related tools, nor does it mention prerequisites such as authentication or watchlist existence. It lacks explicit when/when-not instructions or context for usage.

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