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 behavioral context beyond annotations: it clarifies that the row is deactivated (not deleted), so historical events remain, and enforces ownership. This aligns with destructiveHint=false and readOnlyHint=false, with no contradiction.
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 two efficient sentences, front-loaded with the core verb and resource. Every sentence adds necessary detail without redundancy.
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?
Given the single parameter, no output schema, and presence of annotations, the description is complete: it covers purpose, ownership, and data effect. No gaps remain.
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 a description for the 'id' parameter. The description adds value by specifying that the id is returned by 'subscribe', providing origin context not in the schema.
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 states 'Cancel a subscription by id.' It uses a specific verb (cancel) and resource (subscription), clearly distinguishing it from sibling tools like 'subscribe' and 'list_subscriptions'.
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 to use (to cancel a subscription) and includes ownership enforcement, implying when not to use (cannot cancel others' subscriptions). It does not explicitly list alternatives, but the context is clear.
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.
Several tools are near-clones: ask_pipeworx, ask_pipeworx_beta, and ask_pipeworx_grounded differ mainly by mode, and deep_research overlaps with all of them. The five polymarket_* tools plus bet_research also blur together, and discover_tools vs suggest_questions both serve a 'what can I do' purpose.
All names are readable snake_case, but the convention is mixed: verb-first (get_current_standings, validate_claim, scan_dependency), noun-first (polymarket_edges, pipeworx_trending), and bare verbs (remember, forget, subscribe). The F1 tools follow a clean get_* pattern that doesn't extend to the rest of the set.
35 tools is excessive, especially since the server is named 'F1' but only 4 tools relate to F1. The set could be consolidated substantially: three ask_pipeworx variants, multiple overlapping polymarket scanners, and two tool-discovery helpers all add weight without clear scope.
The F1 side is thin: no qualifying results, constructor standings, lap data, circuits, or driver search by name. The Pipeworx half is broad, but it belongs to a different domain, leaving the overall surface feeling incomplete for either purpose.