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 mark readOnly, idempotent, openWorld. Description adds that it returns specific fields, only active by default with optional include_inactive. No contradictions.
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, no filler. Front-loaded with main action, then usage guidance. Efficient.
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?
Simple tool with good annotations and full schema. Description adds enough context (field list, usage guidance) to be fully useful. No output schema but fields listed inline.
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%, so baseline 3. Description implicitly references the parameter by mentioning 'active subscriptions' vs 'include cancelled', but doesn't add new meaning beyond schema.
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 it 'list the caller's active subscriptions' and enumerates returned fields. 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 advice: 'review what you're monitoring before adding more or to find an id to cancel'. No direct exclusions but context is clear.
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 have overlapping purposes, especially the Pipeworx utilities (ask_pipeworx, ask_pipeworx_grounded, deep_research, etc.). The comic tools are distinct but the large number of similar generally-purpose tools creates confusion across the set.
Comic tools follow a consistent noun pattern (character, characters, issue, issues) but Pipeworx tools mix verb_phrase (ask_pipeworx), noun_phrase (entity_profile), and composite names (scan_competitor_ai_presence). No single convention dominates.
The server name 'Comicvine' suggests a focused comic book reference, yet 30 of 40 tools are unrelated Pipeworx services (company financials, prediction markets, subscriptions, etc.). This is a severe scope mismatch.
The comic-related tools cover characters, issues, volumes, publishers, and creators reasonably well, but the server's overall purpose is diluted by including many non-comic tools that don't form a coherent surface. The comic subset is complete, but the full set is not.