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 critical behavior beyond annotations: 'The row is deactivated (not deleted) so its historical events stay available via recent_alerts.' Annotations indicate non-destructive, idempotent write, which description complements with deactivation detail. No contradiction.
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 main action, then key constraints and side effects. Every sentence adds value with no 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?
Given tool simplicity (1 param, no output schema), description fully covers purpose, usage constraint, and behavioral outcome. No missing information.
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%, so description adds limited extra. However, it ties the 'id' parameter to 'returned by subscribe,' providing useful context that links sibling tools. Baseline 3, uplift to 4 for this context.
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?
Clearly states 'Cancel a subscription by id' with specific verb and resource. Differentiates from siblings like 'subscribe' and 'list_subscriptions' by emphasizing cancellation and ownership.
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 enforcement: 'you can only cancel your own subscriptions.' Provides clear condition for use and implicitly excludes use on non-own subscriptions. No alternative mentioned but context with siblings is clear.
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 substantial overlap among the many question-answering tools (ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, deep_research, validate_claim, compare_entities, entity_profile, recent_changes) and the prediction-market tools (polymarket_arbitrage, polymarket_edges, polymarket_edge_tracker, polymarket_fill_risk, polymarket_kalshi_spread). While each has nuanced differences, agents will struggle to select the right one, especially with several 'ask_pipeworx' variants that behave nearly identically.
Most tool names use snake_case, but patterns vary widely: some are verb_noun (list_feeds, read_feed, subscribe, unsubscribe, remember), others are noun_phrases (polymarket_arbitrage, pipeworx_trending, entity_profile), and a few like 'ask_pipeworx' and 'bet_research' don't follow a consistent structure. The mixed conventions make prediction of new tool names difficult.
With 34 tools, this is far too many for a server named 'Transport Feeds'. The majority of tools are unrelated to transport feeds, covering generic data research, prediction markets, and memory utilities. The count overwhelms any focused purpose and would require extensive discovery to navigate.
For the actual data-research and prediction-market functions, the surface is quite complete—covering lookups, comparisons, grounded verification, arbitrage scans, fill risk, trending, and subscriptions. However, for the declared domain (transport feeds), there are only two feed-specific tools (list_feeds, read_feed) with no write/update/delete operations, leaving obvious gaps.