Remove a specific watchlist from the Alpaca trading platform using its unique identifier to manage portfolio tracking lists.
Delete a specific watchlist by its ID.
| Name | Required | Description | Default |
|---|---|---|---|
| watchlist_id | Yes | watchlist id |
Changes observed during successful MCP inspections.
v2.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, description must disclose behavioral traits. It only states the action 'delete' without mentioning permanence, cascading effects, auth requirements, or error behavior. Minimal value beyond the name.
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 with zero waste; front-loaded verb and object.
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?
Tool is simple with one well-documented parameter; description is adequate for basic usage, though it omits behavioral details like return codes or idempotency, which are not critical given low complexity.
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 covers 100% of parameter with description 'watchlist id', so baseline 3 applies. Description adds no additional meaning to the parameter.
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?
Description uses specific verb 'Delete' with resource 'watchlist' and qualifier 'by its ID', clearly distinguishing from sibling operations like update_watchlist_by_id or get_watchlist_by_id.
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 explicit when-to-use or alternative mention. Usage is implied by the name and action, but the description lacks guidance on prerequisites or distinctions from other watchlist operations.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.