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?
The description adds behavioral context beyond annotations by specifying it returns active subscriptions, enumerates returned fields, and is scoped to the caller. The annotations already declare readOnlyHint, destructiveHint, etc., so the additional field list and scope info are valuable.
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?
The description is three concise sentences, each earning its place: purpose, return fields, and usage guidance. No fluff, front-loaded with the core action.
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?
The tool is simple, has one optional parameter well-described in the schema, and the annotations cover safety. The description fully covers the return values and usage guidance, so it is complete for this 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 description coverage is 100% for the single parameter include_inactive, and the schema already describes it thoroughly. The description does not add any extra meaning about the parameter, so the baseline of 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 'List the caller's active subscriptions,' which is a specific verb+resource. It distinguishes from siblings like subscribe/unsubscribe by focusing on the read-only list operation and mentions 'caller's' to clarify scope.
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?
The description gives explicit use cases: 'Use this to review what you're monitoring before adding more or to find an id to cancel.' It provides clear context for when to use the tool, though it does not explicitly name alternatives or exclusions.
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, with detailed descriptions that specify when to use each. Even overlapping functions like ask_pipeworx varieties are well-differentiated by mode (casual vs grounded vs multi-source).
Most tool names follow a verb_noun snake_case pattern (e.g., query_layer, resolve_entity), but a few deviate with single-word verbs (forget, remember, recall) or noun_noun (layer_info). The pattern is mostly consistent with minor exceptions.
With 33 tools, the count is high and borders on heavy. However, the tools span multiple domains (GIS, financial data, prediction markets, memory, subscriptions), and each serves a unique role, so the count is justifiable but could be streamlined.
The tool set covers a broad range of data access and analysis tasks relevant to the inferred domain of a multi-purpose assistant. While the ArcGIS portion is limited, the overall surface is well-populated with few obvious gaps.