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?
The description adds valuable behavioral context beyond annotations: it states ownership enforcement, that the row is deactivated (not deleted), and that historical events remain available via recent_alerts. This clarifies the non-destructive nature and side effects. It does not contradict any annotation.
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 highly concise: two sentences, front-loaded with the primary action. Every sentence adds meaningful information (ownership, deactivation, historical data). No redundancy or fluff.
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 strong annotations, the description covers the essential behavior: what it does, ownership constraints, and the non-destructive deactivation with historical data retention. It lacks explicit mention of the response format or error cases, but the output schema is absent and annotations cover idempotency and side effects.
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 schema fully describes the single 'id' parameter ('Subscription id (uuid) returned by subscribe'). The description adds no additional parameter detail beyond referencing 'by id', so with 100% schema coverage, a baseline of 3 is appropriate.
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') with a specific verb and resource. It is distinct from the sibling 'subscribe' tool, but does not explicitly differentiate itself from other related tools like 'list_subscriptions' or 'forget'.
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 context of use is implied by the action ('Cancel a subscription'), and ownership enforcement is mentioned. However, there is no explicit guidance on when to use this tool versus alternatives (e.g., 'use subscribe to create, list_subscriptions to view, unsubscribe to cancel'), leaving usage to be inferred.
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 have distinct purposes, but there is some overlap among closely related ones (e.g., ask_pipeworx, ask_pipeworx_grounded, deep_research; multiple Polymarket tools). Descriptions are detailed enough to differentiate, but an agent might still misselect on subtle differences.
Names consistently use lowercase with underscores, but no strong verb_noun pattern. Some are noun-based (airquality, nowcast), others verb-based (ask_pipeworx, compare_entities). This is readable but not perfectly predictable.
35 tools is high but justified by the server's broad scope (data queries, betting analysis, weather, memory, subscriptions). The number feels appropriate given the comprehensive functionality described.
The tool set covers an impressively wide range of capabilities: data querying with multiple modes, entity profiling, comparisons, search, betting analysis, weather, memory, subscriptions, and feedback. Missing features (e.g., updating memories) are minor; the surface is remarkably complete.