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 show non-destructive and idempotent hints, but the description adds crucial context: ownership enforcement, deactivation vs. deletion, and effect on historical events, which are not captured in 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?
Three efficient sentences front-load the action, with no redundant words. Every sentence adds distinct information without verbosity.
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?
For a single-parameter tool with no output schema, the description fully explains the behavior, side effects, and ownership constraints, leaving no gaps for an agent to misunderstand.
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 a clear description for the 'id' parameter. The description adds value by linking the id to the subscribe tool's return, though it does not provide additional format or constraints beyond the schema.
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 explicitly states 'Cancel a subscription by id' with a clear verb and resource, and it distinguishes itself from sibling tools like 'subscribe' and 'list_subscriptions' by specifying ownership enforcement 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?
It provides explicit guidance on when to use the tool ('you can only cancel your own subscriptions') and explains the outcome ('deactivated, not deleted'), helping the agent decide when this tool is appropriate over 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.
Several tools overlap in purpose: ask_pipeworx and ask_pipeworx_beta are explicitly identical today, and the polymarket_edges, polymarket_arbitrage, bet_research, and polymarket_fill_risk tools all orbit market-opportunity analysis from slightly different angles. The descriptions are unusually detailed and often say when to prefer one tool over another, but an agent must read carefully to avoid misselection.
Names are consistently snake_case and mostly follow a verb_noun pattern (list_models, get_model, resolve_entity, validate_claim, scan_dependency), with predictable domain prefixes like polymarket_* and pipeworx_*. A few noun-first names like entity_profile, bet_research, and ai_visibility_check deviate slightly, but the overall convention is readable and coherent.
34 tools is well into the 'too many' range, especially for a server named Openrouter that actually spans several unrelated domains: model catalog, Pipeworx data retrieval, Polymarket analysis, memory, subscriptions, and website tooling. Many individual tools are justified, but the set is overstuffed and would be better split into focused servers.
Each sub-domain is reasonably covered: model catalog has list/get/compare, memory has remember/recall/forget, subscriptions have subscribe/list/unsubscribe/recent_alerts, and Pipeworx querying has multiple modes plus discovery. However, a server named Openrouter exposes no way to actually run completions or route requests through OpenRouter, and the unrelated bundled domains make the overall surface feel scattered rather than complete.