list_subscriptionsList the caller's active subscriptions. Returns id, type, params, created_at, last_fired_at, fire_count for each. Use this to review what you're monitoring before adding more or to find an id to cancel.
| Name | Required | Description | Default |
|---|---|---|---|
| include_inactive | No | Include cancelled subscriptions in the response (default false). |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and idempotentHint=true, so the safety profile is clear. The description adds the return field details, which is helpful but not extensive. No additional behavioral traits (e.g., pagination limits) are disclosed.
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 that are front-loaded and efficient: first sentence states purpose and returns, second gives usage guidance. No redundant language.
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 list tool with no output schema, the description covers purpose, return fields, and usage adequately. It does not mention pagination or error handling, but these are not critical for this tool's simplicity.
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 description coverage is 100% (one parameter with clear description). The description does not add extra meaning beyond the schema; it reinforces the concept of 'active subscriptions' but the parameter is already well-documented.
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 explicitly states 'List the caller's active subscriptions' with clear verb and resource. It also enumerates return fields, distinguishing it from sibling tools like subscribe and unsubscribe.
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 provides clear usage context: 'Use this to review what you're monitoring before adding more or to find an id to cancel.' It implies when to use but doesn't explicitly mention alternatives or when not to use.
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 tools are nearly identical: ask_pipeworx and ask_pipeworx_beta are explicitly the same, and ask_pipeworx, ask_pipeworx_grounded, and deep_research all serve overlapping research/query purposes. discover_tools and suggest_questions both act as discovery entry points, while the five polymarket tools differentiate primarily through intricate details that are easy to confuse.
Naming conventions are mixed across the set: verb_noun (ask_pipeworx, resolve_entity, validate_claim), noun_verb (sheets_append, sheets_create), noun_noun (polymarket_arbitrage, entity_profile), and bare verbs (forget, recall, subscribe). The sheets tools are internally consistent but the broader collection has no uniform pattern, with awkward names like pipeworx_trending and search_within.
With 36 tools, the server exceeds the 25-tool threshold for 'too many'. The Google Sheets portion accounts for only 5 tools, while the majority are highly specialized Pipeworx and Polymarket tools that could be consolidated or dramatically reduced. The count feels inflated relative to the advertised 'Google_sheets' server name and its actual core purpose.
For a server named Google_sheets, the essential operations exist (create, read, write, append, list structure), but there is no delete/clear range tool and no way to add a new sheet to an existing spreadsheet. For the broader data/research scope, important lifecycles are missing (e.g., no direct way to write Pipeworx results into Sheets, no update for subscriptions, only cancel). The set falls short of fully covering either domain.