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, destructiveHint, idempotentHint, and openWorldHint. The description adds the list of return fields and the default active-only scope, providing minor additional context.
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 well-structured sentences: first defines purpose and output, second gives usage guidance. No extraneous words. Highly concise.
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 one optional parameter and no output schema, the description is fully complete. It explains functionality, return fields, and use cases. All necessary information is present.
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% with a clear description for the lone parameter (include_inactive). The tool description does not add new parameter information beyond what the schema provides, so baseline 3 is appropriate.
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 verb 'List', the resource 'subscriptions', and scope 'caller's active'. It also specifies the returned 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?
Explicit guidance: 'Use this to review what you're monitoring before adding more or to find an id to cancel.' This tells when to use the tool and hints at alternatives (subscribe to add, unsubscribe to cancel).
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 have nearly identical purposes: autocomplete and search_suggestions both return query completions, ask_pipeworx and ask_pipeworx_beta are currently identical, and ai_visibility_check overlaps with scan_competitor_ai_presence. The detailed descriptions help for some, but the overlapping clusters create real confusion for an agent selecting a tool.
Naming is a mix of single-word nouns (search, featured, posts, categories) and snake_case verb phrases (resolve_entity, compare_entities, ask_pipeworx), with modifier suffixes like _beta and _grounded. While the snake_case is consistent where used, the overall pattern is not uniform across the server.
38 tools is far too many for a server named 'Tenor' whose core GIF API needs only a handful. Much of the surface belongs to Pipeworx data, polymarket analytics, memory, and subscriptions—scope that belongs in a different server or a clearly separated package.
The Pipeworx side is remarkably complete: query (ask_pipeworx), grounded answers, deep research, entity profiles, comparisons, validation, discovery, memory, subscriptions, and specialized polymarket tools all cover their domain thoroughly. The Tenor side has search, browse, categories, trending, suggestions, and post retrieval—no critical dead ends.