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 indicate read-only, idempotent, non-destructive. Description adds that it returns specific fields and applies only to the caller's subscriptions, complementing annotations well.
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 efficient sentences: one for purpose/output, one for usage guidance. No wasted words.
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?
Fully covers what agent needs: purpose, returned fields, usage context, and parameter effect. No gaps given simplicity and rich annotations.
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 has 100% coverage, including description for 'include_inactive'. The description does not add parameter details beyond schema, baseline 3.
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 verb and resource, and distinguishes from sibling tools like subscribe or 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 when to use: 'review what you're monitoring before adding more or to find an id to cancel', providing clear context and 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.
Most tools target a distinct action or resource, and the long routing descriptions make choices like ask_pipeworx vs ask_pipeworx_grounded vs deep_research clear. The main weak spots are ask_pipeworx_beta being currently identical to ask_pipeworx and the six overlapping Polymarket tools, but each has a discernible workflow.
Naming has internally consistent subfamilies such as censtatd_*, ask_pipeworx*, and polymarket_*, but overall it mixes verb-first names (get_table, validate_claim, subscribe), noun-first names (entity_profile, bet_research, pipeworx_feedback), and bare imperatives (remember, forget, recall). The set is readable but does not follow one convention.
35 tools exceeds the 25+ threshold and feels heavy, especially since many tools (generate_llms_txt, scan_dependency, pipeworx_feedback, pipeworx_trending) are unrelated to the HK Census core implied by the server name. The broad Pipeworx scope explains the width, but the surface is still large for an agent to navigate efficiently.
For a read-only research/data-access gateway, coverage is strong: generic lookup, grounded verification, deep research, entity profile/compare/change, entity resolution, memory, and subscription lifecycle are all represented. Minor gaps exist, such as no subscription update, no explicit bulk/export path, and fewer HK C&SD convenience wrappers, but agents can work around them.