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 provide safety and idempotency info (readOnlyHint, destructiveHint, idempotentHint). Description adds value by specifying return fields (id, type, params, etc.) and default behavior (active subscriptions only). 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 sentences, no wasted words. First sentence states what it does and returns. Second sentence provides usage guidance. Concise and front-loaded.
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 no output schema, description compensates by listing returned fields. Covers purpose, usage, parameter effect, and return values. Complete for a simple list tool with one optional parameter.
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 covers parameter with 100% coverage. Description adds context that default returns active subscriptions and 'include_inactive' extends that, giving semantic meaning beyond just listing the parameter name.
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?
States specific verb and resource: 'List the caller's active subscriptions'. Distinguishes from sibling tools like 'subscribe' and 'unsubscribe' by mentioning purpose: 'review what you're monitoring before adding more or to find an id to cancel.'
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 tells when to use: 'to review what you're monitoring before adding more or to find an id to cancel.' Implicitly indicates not to use when intending to add or cancel subscriptions, guiding towards siblings.
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.
Only 7 of 38 tools are specific to CWE (weakness, children, parents, etc.), while the rest are generic data query, prediction market, and utility tools. This creates massive overlap and confusion: an agent looking for CWE data will encounter many unrelated tools with similar generic names like ask_pipeworx, deep_research, etc.
CWE-specific tools use a consistent noun pattern (weakness, children, parents, etc.), but the remaining tools mix snake_case, camelCase, and no clear pattern (e.g., ask_pipeworx, bet_research, generate_llms_txt). The overall naming is inconsistent.
38 tools is far too many for a CWE server. The vast majority are unrelated to CWE, making the tool surface bloated and unfocused. A concise set of ~5-10 CWE-specific tools would be appropriate.
The CWE-specific tools (weakness, category, view, children, parents, descendants, relationship) cover the main use cases for querying the CWE database. However, the server also includes many unrelated tools that dilute its purpose, making it feel incomplete for someone strictly needing CWE data.