Update Watchlist Group

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

Description aligns with annotations (not read-only, destructive). Adds context on specific modifications (add/remove/replace), which implies potential destructive behavior. No contradictions with annotations.

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?

Single sentence, front-loaded with the core purpose, no redundant information. Every word contributes to understanding the tool's function.

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 output schema covers return values, the description sufficiently covers main use cases. Could mention prerequisites like ownership, but annotations provide destructive hint. Adequate for a 4-param tool.

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 coverage is 100%, but description adds value by explaining the combined usage of 'securities' and 'mode' params (add/remove/replace) and clarifying that 'name' is optional. This goes beyond basic schema descriptions.

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?

Clearly states the action 'Update' on 'watchlist group by id' and specifies the two modification types (rename or modify securities). Distinguishes from sibling tools like create_watchlist_group and delete_watchlist_group.

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?

Provides explicit use cases: rename via 'name' param, or modify securities using 'securities' and 'mode' params. Does not explicitly state when not to use, but the context of siblings implies this is for updates only.

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