add_asset_to_watchlist_by_id

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

No annotations are provided, so the description carries the full behavioral burden. It implies a mutation but never says whether adding a duplicate symbol errors, whether it is idempotent, what permissions are required, or what happens if the watchlist ID is invalid. An output schema exists, so return values are covered elsewhere, but the mutation semantics are not.

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?

A single front-loaded sentence with no filler; the verb and resource come first. It is efficient, though it is terse enough that it omits useful context rather than merely avoiding padding.

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 mutation tool with zero annotations, the description should at minimum cover preconditions and duplicate/error behavior. With an output schema present it need not describe returns, but the missing write-side context leaves the agent unable to predict failure modes.

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%, so both parameters (symbol, watchlist_id) are already documented in the schema. The description's 'by symbol' and 'specific watchlist' phrasing mirrors the schema rather than adding format, case-sensitivity, or validation detail. 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 (add), resource (asset by symbol) and container (a specific watchlist), so the agent knows exactly what the call does. It does not explicitly distinguish itself from remove_asset_from_watchlist_by_id or update_watchlist_by_id, but the name-plus-description pair is unambiguous.

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?

There is no guidance on when to use this versus remove_asset_from_watchlist_by_id or create_watchlist, and no stated preconditions (e.g. the watchlist must already exist, the symbol must be valid/tradable). The description just restates the operation with no usage context.

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