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 and destructiveHint; description adds that the row is deactivated but not deleted, preserving historical events. 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?
Two concise sentences front-loading the main action, with no extraneous information.
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 simple tool (single parameter, no output schema), the description fully covers purpose, ownership, and behavioral consequences.
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% and the parameter 'id' is self-explanatory with its schema description. The tool description adds no additional semantic value for the parameter.
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') and the resource ('by id'). It distinguishes from sibling tools 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') and explains the effect (deactivation, not deletion). However, it does not mention when not to use or compare to alternatives.
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 with clear descriptions, but the multiple ask_pipeworx variants and several Polymarket tools could cause initial confusion. An agent reading carefully can differentiate them, but the similarity in themes requires attention.
Names use a mix of conventions: verb_noun (ask_pipeworx, compare_entities), noun_noun (entity_profile, dataset_columns), and single verbs (remember, forget). While some subgroups have internal consistency (e.g., polymarket_*), there is no overall predictable pattern.
With 34 tools, the count exceeds the 'too many' threshold of 25. While the server is comprehensive, the large number of highly specific tools (especially for prediction markets) feels overwhelming and could confuse agents.
The tool set covers a wide range of capabilities: data querying, entity resolution, company analysis, prediction markets, memory, subscriptions, and validation. Minor gaps exist (e.g., no data writing tools), but for the read-heavy analytical purpose, it is nearly complete.