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?
Describes deactivation (not deletion) behavior, adding context beyond annotations. No contradictions.
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 efficient sentences, front-loaded with action, no wasted words.
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?
Covers all key aspects: action, ownership, side effect, and relation to sibling tool. Complete for a simple single-param tool.
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 covers 100% of param, description doesn't add new info beyond 'by id'. Baseline 3.
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?
Clear verb+resource: 'Cancel a subscription by id.' Distinguishes 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?
Explicit ownership enforcement and explanation that deactivation preserves history, steering users to 'recent_alerts' for historical data.
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.
Tools have distinct purposes but some overlap exists, e.g., multiple ask_pipeworx variants and deep_research could confuse an agent. Prediction market tools are differentiated but not immediately obvious.
Names are consistently in snake_case but mix verb and noun orders (e.g., 'ai_visibility_check' vs 'ask_pipeworx'). No strict verb_noun pattern throughout.
34 tools is on the high side but still reasonable given the broad domain coverage. Some tools could be consolidated without loss.
Covers data querying, company research, prediction markets, subscriptions, and memory. Minor gaps like no direct web search but ask_pipeworx substitutes.