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 and destructiveHint, so the description adds value by noting the default behavior (active only) and the parameter effect. No 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: first defines purpose and output, second gives usage guidance. No filler.
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 with one optional parameter and no output schema, the description is complete: covers return fields, default behavior, and practical use case.
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 doesn't add meaning beyond the schema's existing parameter description. Baseline 3 applies.
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 it lists the caller's active subscriptions and enumerates return fields. Distinguishes from sibling tools like subscribe and unsubscribe through the usage context.
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 says when to use: 'review what you're monitoring before adding more or to find an id to cancel.' No exclusions, but provides clear context and contrasts with subscribe/unsubscribe.
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.
Multiple tools occupy nearly identical roles: ask_pipeworx, ask_pipeworx_beta (explicitly identical right now), ask_pipeworx_grounded, and deep_research all answer research questions; polymarket_edges, bet_research, and polymarket_arbitrage overlap heavily on prediction-market opportunities; entity_profile, compare_entities, and recent_changes overlap on company research. The detailed descriptions help, but the clusters create real misselection risk.
Nearly all tools follow a readable snake_case convention, many with verb_noun structure (resolve_entity, list_subscriptions, validate_claim, scan_dependency). Minor deviations exist: tankerkoenig_stations_nearby plural vs tankerkoenig_station_details/prices singular, plus noun-style names like pipeworx_feedback and pipeworx_trending, but the overall pattern is predictable.
34 tools is heavy, and the problem is compounded by the server being named Tankerkoenig: only 3 of the 34 tools relate to German fuel prices while the other 31 are an unrelated Pipeworx/Polymarket/memory/subscription toolkit. This is a sprawling, unfocused surface rather than a well-scoped set.
For the nominal Tankerkoenig domain, stations_nearby + station_details + prices cover core lookups, though station search by name and price history are missing. For the broader bundled data/prediction-market domain, coverage is extensive but has notable gaps such as no trade execution, no general web search, and several redundant access paths that complicate the surface.