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-readOnly, non-destructive, and idempotent. The description adds valuable behavioral context: the row is deactivated (not deleted) and historical events remain accessible via recent_alerts, which is beyond what annotations provide. No contradiction 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?
The description is two sentences with front-loaded purpose ('Cancel a subscription by id'), immediately followed by constraints and behavioral details. Every sentence provides critical information without extraneous 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?
Given the tool's simplicity (1 parameter, no output schema, annotations present), the description fully covers purpose, ownership constraint, persistence behavior, and relationship to other tools. No gaps remain for this complexity level.
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 has 100% coverage with the single parameter 'id' described as 'Subscription id (uuid) returned by subscribe.' The description adds context by stating the id is returned by subscribe, linking to the subscription creation flow. This adds meaning beyond the schema alone.
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 the action ('cancel a subscription by id') and the resource ('subscription'). It distinguishes from siblings like subscribe and list_subscriptions by specifying cancellation and deactivation behavior.
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 explicitly notes ownership enforcement ('you can only cancel your own subscriptions'), which guides when the tool is applicable. It also implies that recent_alerts should be used for historical events after cancellation. However, it does not provide explicit when-not-to-use guidance or alternatives beyond the implication.
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 distinct purposes, such as `entity_profile` for company profiles and `recent_changes` for updates. However, some overlap exists between `ask_pipeworx` and `ask_pipeworx_grounded` (both query data, one with hallucination resistance), and among Polymarket-related tools (`bet_research`, `polymarket_edges`, `polymarket_arbitrage`). Detailed descriptions help distinguish them.
All tool names follow a consistent snake_case pattern (e.g., `ai_visibility_check`, `ask_pipeworx`, `bet_research`, `compare_entities`). No mixing of camelCase or other conventions. The names are descriptive and predictable.
At 29 tools, the server is on the heavy side. While each tool serves a specific function, the broad scope (color naming, Polymarket betting, company research, etc.) makes the count feel slightly high for a single server, though still manageable.
The tool set covers color naming, company research, Polymarket, AI visibility, memory, subscriptions, and data queries comprehensively. Minor gaps exist (e.g., no direct SEC filing retrieval without compound tools), but overall it provides a well-rounded surface for its diverse domain.