Delete one of your Stock Trackers permanently, along with every instrument in it. If it was public, its followers lose it too. This cannot be undone.
| Name | Required | Description | Default |
|---|---|---|---|
| watchlist | Yes | Name, slug or id of the Stock Tracker to delete. | |
| confirm_name | Yes | The exact name of the Stock Tracker, typed back, to confirm the deletion. Ask the user for it — do not fill this in on their behalf. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already mark destructiveHint=true, but the description adds critical layers: cascading deletion of all instruments, followers losing access if public, and irreversibility ('This cannot be undone'). This goes well beyond the annotations and fully explains the behavioral impact.
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?
Two sentences with no fluff: the first states the primary action and consequence, the second adds follower impact and permanence. Every word earns its place.
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 destructive tool with no output schema, the description covers all critical context: what gets deleted, cascade effects, follower consequences, and irreversibility. It is sufficient for an agent to decide whether to invoke and what to communicate to the user.
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%, with both parameters clearly described (watchlist identity, confirm_name with explicit user-confirmation instructions). The description adds no direct parameter-level meaning beyond the schema, so it sits at the baseline of 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 tool deletes a Stock Tracker permanently, along with every instrument in it, which is a specific verb+resource+scope. It distinguishes from siblings like remove_from_watchlist (removes an instrument) and unfollow_watchlist (changes follower status).
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 usage context is clear: use this for permanently deleting a whole watchlist, not for removing individual instruments (which would be remove_from_watchlist). It implies the destructive scope but does not explicitly name alternatives or exclusions, so it misses a 5.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
With 57 tools, most have distinct purposes (market data, journaling, watchlists). A few related tools (get_price_alignment vs get_crypto_price_alignment, get_market_pulse vs get_market_movers) could cause miselection, but descriptions clarify asset types and scope.
Tools predominantly use get_/list_/create_/update_/delete_ verbs with clear noun suffixes. Minor deviations like start_here, whoami, add_to_watchlist, and remove_from_watchlist break the pure verb_noun pattern, but the style is consistent and readable.
At 57 tools, the server is far beyond the well-scoped range. While the domain is broad, this many tools will overwhelm an agent's capability to select accurately, and many could be consolidated (e.g., separate financial statements).
The server covers watchlist CRUD, trading journaling, market data (fundamentals, statements, news, transcripts), analysis tools, and community features. No obvious dead ends; lifecycle coverage is thorough for the described domain.
