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?
The description adds crucial behavioral details beyond annotations: the row is deactivated (not deleted) and historical events remain available via recent_alerts. This complements the idempotentHint and destructiveHint annotations without 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, each providing essential information: the action (cancel), constraint (ownership), and side effect (deactivation vs deletion). No redundancy or unnecessary 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 covers the core function, constraints, and behavioral nuance. However, it does not mention the return value or confirmation, which could be helpful for a mutation tool. Given the presence of sibling tools and annotations, it is nearly 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?
The input schema already fully describes the single parameter 'id' with its type and origin ('Subscription id (uuid) returned by subscribe'). The description does not add new meaning, so baseline 3 applies (schema coverage 100%).
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 the tool cancels a subscription by ID, and distinguishes it from siblings like subscribe (creation) and list_subscriptions (listing). The verb 'Cancel' and resource 'subscription' are specific.
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 specifies ownership enforcement ('you can only cancel your own subscriptions'), which guides appropriate usage. It does not explicitly list when not to use or mention alternatives, but the context is clear for a straightforward cancellation.
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 overlapping purposes: ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, and deep_research all answer queries, and the multiple polymarket_* tools scan for edges and arbitrage. The Drive tools are distinct, but the surrounding 31 unrelated tools create significant ambiguity about which tool to call for a given task.
Tool names are all snake_case, but the pattern is inconsistent: some start with verbs (drive_create_file, ask_pipeworx, validate_claim), some are noun phrases (entity_profile, recent_changes, polymarket_edges), and some are bare verbs (remember, forget, recall). There is no uniform verb_noun convention, and suffixes like _beta and _grounded add further irregularity.
36 tools is far too many for a server named Google_drive, especially since only 5 tools (drive_create_file, drive_get_content, drive_get_file, drive_list_files, drive_search) actually relate to Drive. The other 31 tools cover unrelated domains like Pipeworx data queries, Polymarket betting, and memory management, making the tool count wildly disproportionate to the server's apparent purpose.
For a Google Drive server, the tool set is incomplete: it covers create, get content, get metadata, list, and search, but lacks essential operations like updating, deleting, uploading, moving, copying files, creating folders, or managing permissions/sharing. These gaps would force agents to work around missing core Drive functionality.