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 mark it as non-destructive and non-read-only, but the description adds crucial details: ownership enforcement and that the row is deactivated rather than deleted. This clarifies the actual effect and preserves historical data, going beyond the annotations. No contradiction found.
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, front-loaded with the primary action, then behavioral caveats. Every sentence provides essential information 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?
With one parameter, comprehensive annotations, and no output schema, the description covers purpose, ownership constraint, and post-cancellation behavior. It is sufficiently complete for the tool's simplicity.
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 documents the single 'id' parameter, including its type and origin from subscribe. The description only says 'by id,' adding no new semantics beyond the schema. Baseline of 3 applies given 100% schema coverage.
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 opens with 'Cancel a subscription by id,' providing a specific verb and resource. It clearly distinguishes from sibling tools like subscribe and list_subscriptions, and clarifies the action is a cancellation, not deletion.
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 states ownership is enforced, giving a clear condition for when the tool can be used. It mentions recent_alerts as a way to access historical events, implying an alternative but doesn't explicitly compare to other subscription tools. Overall, it gives solid contextual guidance but lacks explicit when-to-use phrasing.
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.
Many tools have overlapping purposes, e.g., five 'ask_pipeworx' variants and multiple prediction market tools with subtle distinctions. An agent would struggle to pick the correct tool without careful reading of long descriptions.
Most tools follow a verb_noun pattern with domain prefixes (pipeworx_, polymarket_, pulsedive_), but a few standalone verbs (forget, recall) break the pattern slightly. Overall consistent within groups.
33 tools is on the heavy side, but the server covers a broad range of domains (data querying, prediction markets, security, subscriptions). The count is borderline but not excessive given the scope.
The tool set covers a wide array of operations: querying, entity analysis, comparisons, prediction market edge detection, subscriptions, memory, and scanning. Minor gaps exist (e.g., limited to Polymarket/Kalshi for prediction markets), but overall the surface is comprehensive.