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?
Annotations provide idempotentHint=true and destructiveHint=false. The description adds crucial context: the row is deactivated (not deleted), historical events persist via recent_alerts, and ownership is enforced. No contradictions with annotations.
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, no filler. First sentence states core action, second adds essential constraints. Every word earns its place.
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 one-parameter tool with no output schema, the description covers the purpose, constraints, and side effects (soft delete, impact on historical data). It references related tool 'recent_alerts' for continuity.
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 clear description of the 'id' parameter as 'Subscription id (uuid) returned by subscribe.' The description does not add additional meaning to the parameter itself beyond the schema, so baseline score 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 'Cancel a subscription by id' using a specific verb and resource. It distinguishes from sibling tools like 'subscribe' (create) and 'list_subscriptions' by focusing on cancellation and soft deactivation.
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 implies when to use: to cancel one's own subscription. It mentions ownership enforcement and that historical events remain available, but does not explicitly state when not to use or name alternatives. Given sibling context, it's sufficiently 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 tool clusters have overlapping purposes: the three ask_pipeworx variants are nearly identical, polymarket_edges and polymarket_arbitrage both scan for opportunities, and ai_visibility_check vs scan_competitor_ai_presence create confusion. Although descriptions are detailed, an agent could easily misselect among these.
Most tools follow snake_case verb_noun (get_article, search_journals, resolve_entity), but there are brand-prefixed names (ask_pipeworx*, pipeworx_trending, pipeworx_feedback) and noun-phrase tools (entity_profile, bet_research) that break the pattern. The three ask_pipeworx variants are consistently named but confusable.
35 tools is excessive for a coherent server, especially one where many tools are meta-routes (ask_pipeworx, deep_research) that could consolidate functionality. The count exceeds the 25-tool threshold for 'heavy' and includes several one-off tools (generate_llms_txt, scan_dependency) that don't fit the dominant data-access theme.
The DOAJ subset is complete for read-only search and retrieval, but the server lacks a clear domain: it mixes DOAJ, prediction markets, memory, and subscriptions. For the broader Pipeworx platform, there are some dead ends (e.g., no subscription editing, no raw historical market data, no batch tools), and the non-DOAJ tools create confusion about what the server is actually for.