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, idempotentHint=true, destructiveHint=false. Description adds minor behavioral detail (returns specific fields) but doesn't contradict annotations. Value added beyond annotations is moderate.
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 concise sentences that front-load purpose and usage. Every sentence contributes value; no extraneous content.
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?
Given simple schema (one optional param, no output schema) and annotations covering safety, the description sufficiently informs the agent about what the tool does and when to use it.
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 covers the single parameter (include_inactive) with full description. Description implicitly references it by saying 'active subscriptions' but adds no new meaning.
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 'List the caller's active subscriptions' with specific return fields (id, type, params, created_at, last_fired_at, fire_count). Distinguishes from siblings 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?
Provides explicit when-to-use guidance: 'review what you're monitoring before adding more or to find an id to cancel.' Suggests context but doesn't explicitly name sibling tools as alternatives.
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 serve overlapping research purposes (ask_pipeworx, ask_pipeworx_grounded, deep_research, validate_claim, entity_profile, compare_entities), which could confuse an agent. However, descriptions help differentiate them by use case (single vs multi-part, grounded vs standard, etc.). Some overlap remains.
Tool names mix patterns: some are verb_noun (ask_pipeworx, bet_research), others are noun_phrase (price_feed, recent_alerts) or adjective_noun (ticker_v2). No strong naming convention, but all use snake_case consistently, making them readable.
40 tools is on the high side for a single server, covering both Gemini exchange data and Pipeworx's broad knowledge tools. While each tool serves a purpose, the scope feels broad, and some tools could be separated into dedicated servers.
The Gemini exchange tools cover essential read-only data (order book, candles, ticker, trades), but lack order placement, likely intentionally. The Pipeworx tools provide extensive research capabilities across many domains, leaving few gaps for the stated purposes.