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 that the row is deactivated (not deleted), complementing annotations (destructiveHint=false). Adds ownership enforcement detail beyond 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 concise sentences, front-loaded with purpose, efficiently conveying all necessary information without waste.
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 covers purpose, ownership, side effects, and relation to sibling tool, making it complete.
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%. The description does not add parameter details beyond the schema's own description, which is already clear.
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 'Cancel a subscription by id', specifying the verb and resource. It distinguishes from siblings like subscribe and list_subscriptions by emphasizing ownership and 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?
Provides clear context: ownership enforcement and deactivation semantics. Mentions historical data via recent_alerts, hinting at when to use that sibling tool instead.
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.
Many tools have clear distinct purposes, but ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, and deep_research have overlapping functionality with subtle differences, causing potential confusion. Overall, most tools are distinguishable.
Tool names use a mix of patterns: some follow verb_noun (validate_claim, resolve_entity), others are compound nouns (polymarket_arbitrage, ai_visibility_check), and some are plain verbs (recall, forget). Inconsistent style and length reduce predictability.
At 34 tools, the count is on the high side for a typical server, but it might be manageable if the scope were broad. However, the server name 'Opentreeoflife' suggests a narrow biological focus, making the large count feel mismatched and excessive.
For a server named after a tree-of-life database, only three tools (match_names, common_ancestor, taxon_info) are relevant. Missing fundamental operations like listing children, searching taxa, or retrieving phylogenetic trees leaves the domain severely incomplete.