unified_remove_from_watchlist

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

No annotations are provided, and the description does not disclose behavioral details such as whether removal is permanent, required permissions, or error handling. The brief 'across supported brokers' adds some context but is insufficient.

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 short and front-loaded with the action. The Args section is structured but repeats parameter names; could be slightly more concise by integrating into the paragraph.

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 presence of an output schema, the description does not mention return values or behavior. It also fails to address error conditions or broker-specific caveats, leaving gaps for an AI agent.

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?

With 0% schema description coverage, the description adds value by explaining parameters: 'Name of the watchlist', 'List of stock symbols to remove', and 'Optional list of broker names to target'. This clarifies purpose beyond the schema titles and types.

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 tool removes symbols from a watchlist, with the verb 'removes' and resource 'symbols from a watchlist'. It distinguishes itself from siblings like 'remove_from_watchlist' by mentioning 'across supported brokers', implying cross-broker functionality.

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?

No guidance on when to use this vs alternatives such as 'remove_from_watchlist' or 'unified_add_to_watchlist'. The description lacks context about prerequisites or scenarios.

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