Delete one of the caller's custom signals. Cascade-safe by default: refused with 409 if another custom signal references it (the error lists the referencing signals). Pass force: true to delete anyway — existing references will break on next recompile. Available on every plan.
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | Custom signal slug. | |
| force | No | When true, skip the reference check and delete anyway. Default false. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description fully covers behavioral traits: cascade-safe default, error response with referencing signals, force option effect, and subsequent reference breakage on recompile. No contradictions.
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 three sentences, immediately stating the primary action, then detailing edge cases and plan availability. No unnecessary words.
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?
The description covers core behavior, error handling, and force option. It does not describe the success response, but as a delete operation this is sufficient given no output schema.
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% so baseline is 3. The description adds context beyond the schema: explains the cascade behavior for `force` and the error listing, making the tool's behavior clearer.
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 ('Delete one of the caller's custom signals') and differentiates from sibling tools (e.g., create, update) by specifying ownership ('caller's') and the specific resource.
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 explains when the tool will refuse (409 if referenced) and how to force deletion. It does not explicitly name alternatives but implies that deletion should be avoided if references exist unless forced.
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.
Most tools target distinct resource-action pairs, but get_ticker and get_ticker_history overlap (both return a single historical row via asof), and the four subscribe_* tools are thin wrappers around create_webhook, creating some ambiguity. Detailed descriptions mitigate but don't eliminate confusion.
The tickerbot_ prefix and verb_noun pattern are consistent (create_*, get_*, list_*, delete_*, update_*), but subscribe_* deviates from create_* for webhooks, and scan/search_news are bare verbs. Overall predictable.
35 tools is excessive for the domain; many could be consolidated (e.g., four subscribe_* variants into a single parameterized webhook creator, get_ticker/get_ticker_history into one). The breadth of data types justifies some volume, but this exceeds the 25-tool threshold for coherence.
Full lifecycle coverage for universes, custom signals, and webhooks; extensive read-side for tickers, series, bars, events, news, and scans. No critical dead ends: anything creatable can be updated/deleted/tested, and data lookups have appropriate query tools.
