unsubscribeCancel a subscription by id. Ownership is enforced — you can only cancel your own subscriptions. The row is deactivated (not deleted) so its historical events stay available via recent_alerts.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Subscription id (uuid) returned by subscribe. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Discloses that the row is deactivated (not deleted) and historical events remain available via recent_alerts. This adds context beyond annotations, which already indicate non-destructive mutation.
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, each adding essential information: action and ownership, then side effect. No fluff, front-loaded with the core purpose.
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 simple, single-parameter tool with good annotations, the description covers purpose, ownership constraints, and behavioral consequences. No gaps for the given 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?
The input schema already fully describes the single parameter 'id' with clear description. The tool description adds no further parameter details, making it adequate but not exceptional.
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 ('Cancel a subscription by id') and the resource ('subscription'). It distinguishes from sibling tools like 'subscribe' and 'list_subscriptions' by focusing on cancellation.
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?
Explicitly says ownership is enforced ('you can only cancel your own subscriptions'), which guides appropriate usage. Also explains the deactivation behavior, helping the agent understand when this tool is applicable.
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.
Multiple tool families overlap heavily: ask_pipeworx/ask_pipeworx_beta/ask_pipeworx_grounded all route through the same 5,721 tools, polymarket_edges/polymarket_arbitrage/bet_research/polymarket_fill_risk all target prediction-market opportunities, and ai_visibility_check vs scan_competitor_ai_presence cover the same probe. An agent would struggle to pick the right one without reading every description carefully.
There are coherent subfamilies (ask_pipeworx_*, polymarket_*, remember/recall/forget, list/read/fetch_feed), but the overall set mixes verb-first names (list_feeds, validate_claim, fetch_feed) with noun-first names (entity_profile, bet_research, deep_research) and adjective-led names (recent_alerts, recent_changes). The inconsistency is noticeable but not chaotic.
34 tools is heavy for a server branded 'Law Feeds,' and many tools are off-domain (Polymarket betting, npm dependency scanning, AI visibility marketing, generic memory). The breadth could justify a larger catalog, but the overlapping research/Polymarket tools inflate the count beyond what the surface needs.
As a general data-gateway, the set is fairly complete: routing, grounded answers, deep research, entity resolution, comparison, subscriptions, memory, and feedback are all covered. Relative to the 'Law Feeds' identity, though, the surface is shallow — only list_feeds, read_feed, and fetch_feed serve that purpose, with no feed search, management, or update capabilities.