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, idempotentHint, and destructiveHint. Description adds value by listing the exact return fields and mentioning the optional parameter, providing extra behavioral context beyond annotations.
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, front-loaded with action, no unnecessary words. Efficient and clear.
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 tool with one optional param and no output schema, description includes return fields and usage guidance, covering all necessary context.
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% (single parameter fully described). Description does not add extra meaning beyond schema, so baseline of 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?
Description clearly states 'List the caller's active subscriptions' – specific verb and resource. Includes return fields, differentiating 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?
Explicitly advises use 'to review what you're monitoring before adding more or to find an id to cancel', giving clear context for when to use this listing tool.
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.
Each tool has a clearly distinct purpose, even within clusters like Pipeworx queries (ask_pipeworx vs ask_pipeworx_grounded vs deep_research) and Polymarket tools (bet_research, arbitrage, edges, etc.). Overlap is minimal and explicitly addressed in descriptions.
All tool names use snake_case, and most follow a consistent verb_noun pattern (e.g., ask_pipeworx, compare_entities, resolve_entity). Exceptions like remember, reverse are still single words in the same style.
32 tools is on the high side but justified by the wide scope: data querying, betting, memory, subscriptions, and utilities. Each tool earns its place, and the count is not excessive given the breadth.
The tool set covers the core workflows of querying structured data, comparing entities, validating claims, scanning dependencies, and monitoring, with few gaps (e.g., no direct data visualization). Minor gaps exist but are manageable.