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 give idempotentHint=true and destructiveHint=false; description adds that row is deactivated not deleted, preserving history. No contradictions, detailed side effect disclosure.
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 covering purpose, constraint, and side effect with no extraneous 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?
Complete for a simple one-param tool with no output schema. Covers purpose, ownership, and behavioral impact (deactivation).
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 describes 'id' as subscription uuid from subscribe; description reinforces its source and requirement. Since schema coverage is 100%, description adds useful context beyond 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?
Description clearly states 'Cancel a subscription by id' with specific verb and resource. Differentiates from siblings like 'subscribe' and 'list_subscriptions' by implying mutation.
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 constraint ('you can only cancel your own subscriptions'), guiding when the tool is applicable. Does not explicitly mention alternatives or when not to use, but constraint 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 significant overlap among tools, particularly within the Pipeworx family (ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded) and the Polymarket family (polymarket_arbitrage, polymarket_edges, polymarket_edge_tracker, polymarket_fill_risk, polymarket_kalshi_spread). These tools have similar purposes, making it hard for an agent to distinguish them at a glance. The Gmail tools are a small, distinct cluster, but the overall set is confusing.
All tool names use snake_case, but the verb_noun pattern is inconsistent. Many start with verbs (ask_pipeworx, compare_entities, discover_tools, etc.), but some use noun_verb (bet_research), noun_noun (entity_profile), or adjective_noun (deep_research). This mixed pattern reduces predictability.
With 36 tools, the count is high, but the server name 'Gmail' suggests a focused email service. Only 5 tools are Gmail-related, while the rest cover a vast, unrelated domain (Pipeworx, Polymarket, etc.). This mismatch makes the tool count inappropriate for the server's apparent purpose.
For the Gmail domain, the tool surface is incomplete (e.g., missing delete, archive, modify labels). For the broader Pipeworx/Polymarket domain, the tools are extensive but lack clarity in coverage. The server attempts to cover too many domains without sufficient depth in any, leading to notable gaps.