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?
Description adds significant behavioral context beyond annotations: ownership enforcement, deactivation vs deletion, historical events staying available. Annotations (destructiveHint=false) are consistent.
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 with no wasted words. Efficiently communicates purpose, constraints, and behavioral nuance.
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 simple mutation tool with one param, description covers purpose, usage, behavior, and side effects. No gaps given annotations and schema richness.
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?
Single parameter 'id' is fully described in schema coverage (100%). Description does not add additional meaning beyond schema, so baseline score of 3.
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.' Specific verb (cancel/unsubscribe) and resource (subscription). Distinguishes from siblings 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 enforcement and that the row is deactivated, not deleted. Provides context on when to use (own subscriptions) and behavior, though no explicit alternative tool mentioned.
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 groups (ask_pipeworx/ask_pipeworx_grounded/deep_research, conditions/disease_names, polymarket_* family) have overlapping purposes, requiring careful reading of descriptions to differentiate. While many tools are conceptually distinct, the similarity within domains could lead to agent misselection.
Naming is mostly snake_case but patterns vary: verb_noun (ask_pipeworx), noun_noun (entity_profile), single verb (forget, recall), and some adjectives (recent_changes). No consistent structure across the set, though individual names are descriptive.
With 40 tools, the server is overly large for typical coherence. The tool count exceeds the 15–25 range deemed borderline, making it hard for agents to navigate and select efficiently.
The surface covers medical coding (ICD, LOINC, UCUM, drugs, procedures), financial data, prediction markets, memory, subscriptions, and meta-tools. Missing but minor elements (e.g., CPT codes) do not significantly hinder common workflows.