tv_watchlist_add_symbol

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

The description repeats the destructive annotation but introduces ambiguity by saying 'via the star button' which may not apply in automated contexts. The parameter description says 'informational; adds the active chart symbol' while the tool description says 'current chart symbol', causing slight confusion about the parameter's role.

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 one sentence plus a warning, with no wasted words. Front-loaded with the key action.

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 simple tool with clear schema and annotations, the description covers the essential purpose and side effect. It lacks details like idempotency or what happens if symbol already exists, but given the simplicity, it is reasonably 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?

The single parameter is fully described in the input schema (100% coverage), so the description adds no additional meaning. It stays at baseline 3.

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 action: add the current chart symbol to the watchlist. It distinguishes from sibling tools like tv_watchlist_read and tv_watchlist_sync.

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 includes a DESTRUCTIVE label, warning that it modifies the watchlist, but does not provide explicit when-to-use or alternative tools. The destructive hint is useful but not comprehensive.

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