unified_add_to_watchlist

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

With no annotations provided, the description carries full burden for behavioral disclosure. It only states the action (adds symbols) without covering side effects (e.g., idempotency, watchlist creation, error conditions, permissions, or rate limits). Critical behavioral details are missing.

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 two sentences: a concise summary followed by a structured argument list. No unnecessary words. Information is front-loaded and well-organized.

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's complexity (unified across brokers, 3 parameters, output schema exists), the description covers basic purpose but omits important context like default broker behavior, watchlist existence requirements, and error scenarios. It is adequate but not 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 0%, so the description must compensate. It provides brief parameter descriptions (e.g., 'List of stock symbols to add' clarifies symbols are stock symbols, 'Optional list of broker names to target' clarifies optionality). This adds basic meaning but lacks constraints, format, or examples.

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 'Adds symbols to a watchlist across supported brokers,' specifying the verb (adds), resource (symbols to watchlist), and scope (across supported brokers). This distinguishes it from sibling 'add_to_watchlist' which likely operates on a single broker.

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 does not provide any guidance on when to use this tool versus alternatives like 'add_to_watchlist', nor does it mention prerequisites, exclusions, or optimal use cases. It merely describes the action without contextual usage advice.

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