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?
Discloses important behavior beyond annotations: 'The row is deactivated (not deleted) so its historical events stay available via recent_alerts.' No contradiction with annotations (readOnlyHint false, destructiveHint false).
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 purpose. Every sentence adds value: purpose, constraint, and effect. 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?
Simple tool with one parameter and no output schema. Description covers purpose, constraint, and side effect. Adequate 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?
Schema coverage is 100% with parameter description. The tool description does not add significant new meaning beyond the schema's 'Subscription id (uuid) returned by subscribe.' Baseline 3 is appropriate.
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 verb 'Cancel' and resource 'subscription by id', distinguishing it 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?
Explicitly states 'Ownership is enforced — you can only cancel your own subscriptions', providing clear context for when to use. Does not mention explicit alternatives or when not to use, but the constraint is strong enough.
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.
There is notable overlap between tools like ask_pipeworx, ask_pipeworx_beta, and ask_pipeworx_grounded, as well as between polymarket_edges and bet_research. While descriptions differentiate them, an agent may struggle to pick the right one without deep understanding of nuances.
Tool names use mixed conventions: snake_case (ai_visibility_check), verb_noun (ask_pipeworx, bet_research), and single-word verbs (forget, recall). Some names are very long (polymarket_fill_risk) while others are terse, reducing predictability.
33 tools is high but can be justified by the broad domain coverage (data retrieval, entity resolution, comparisons, memory, subscriptions). However, several tools serve similar purposes, suggesting potential consolidation.
The tool set covers a wide range of data sources and tasks (SEC, FDA, real estate, prediction markets, etc.) with CRUD-like operations on memory and subscriptions. Minor gaps exist, such as no direct stock trading or social media monitoring, but overall coverage is strong.