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 indicate readOnlyHint=false, destructiveHint=false, idempotentHint=true. The description adds valuable context: 'The row is deactivated (not deleted) so its historical events stay available via recent_alerts.' No contradictions.
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 the main action ('Cancel a subscription by id.'), 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?
The description explains the outcome (deactivation, preservation of historical events) and covers the single required parameter. No output schema needed as behavior is fully described.
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 description for 'id'. The description mentions 'by id' and 'returned by subscribe', which reinforces the schema but does not add significant new meaning beyond it.
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 states 'Cancel a subscription by id.' with a specific verb and resource, and it distinguishes from sibling tools like 'subscribe' and 'list_subscriptions' by focusing on cancellation.
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 states ownership enforcement ('you can only cancel your own subscriptions'), providing clear context for when to use. It lacks explicit exclusions but is still 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.
Several tool clusters overlap heavily: ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, deep_research, discover_tools, and suggest_questions all serve query/discovery purposes; polymarket_edges, polymarket_arbitrage, polymarket_edge_tracker, polymarket_fill_risk, and bet_research all target prediction-market opportunity detection. ask_pipeworx_beta is explicitly identical to ask_pipeworx right now, making the distinction essentially invisible without deep description parsing.
Names mix domain prefixes (oc_*, polymarket_*, pipeworx_*), action verbs (validate_claim, resolve_entity, generate_llms_txt), and plain nouns (entity_profile, recent_alerts, recent_changes). Most are readable snake_case, but there is no uniform verb_noun or domain-first convention, so the set feels stylistically fragmented rather than patterned.
35 tools is a heavy surface for a server ostensibly named 'Open Contracting' — only 4 of the 35 tools actually relate to open contracting data. The rest sprawl across general data lookup, prediction markets, memory, subscriptions, npm scanning, and AI visibility, making the tool count feel bloated and unfocused relative to the stated purpose.
For the open-contracting domain implied by the server name, the surface is incomplete: there is coverage metadata, search, recent releases, and process history, but no direct retrieval of a single release by ID and no broader OCDS exploration tools. As a general data/Pipeworx toolkit the coverage is wide, but the severe mismatch between the server name and the actual tool set creates a significant gap between expectation and capability.