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 already indicate non-read-only, non-destructive, and idempotent. The description adds that the row is deactivated (not deleted) and historical events remain via recent_alerts, providing useful behavioral nuance beyond 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 wasted words. All information is front-loaded and relevant.
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 tool with one parameter and no output schema, the description explains ownership, deactivation mechanism, and connection to recent_alerts. No gaps.
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 covers 100% of parameters with a description for 'id' ('Subscription id (uuid) returned by subscribe'). The description does not add new semantic information beyond implying cancellation by id, which is already clear from 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,' providing a clear verb (cancel) and resource (subscription). It distinguishes itself from siblings 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?
It specifies ownership enforcement ('you can only cancel your own subscriptions'), giving clear context for when to use. It does not explicitly mention when not to use alternatives, but the context is sufficient.
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 clearly distinct purposes, but there is some overlap among the meta-querying tools like ask_pipeworx, ask_pipeworx_grounded, deep_research, and discover_tools, which could cause confusion for an agent deciding which to use.
Tool names use a mix of verb_noun and noun patterns, with snake_case throughout but no single consistent structure (e.g., ask_pipeworx vs. bet_research vs. dataset). The naming is readable but not uniform.
At 33 tools, the count is on the higher side but justifiable given the broad scope of the Pipeworx platform, covering data querying, entity analysis, prediction markets, memory, subscriptions, and feedback.
The toolset covers a wide range of data sources and operations, including querying, entity profiling, comparisons, prediction market analysis, and monitoring. Minor gaps exist (e.g., no direct SEC filing viewer), but the meta-tools handle these adequately.