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 and idempotent. The description adds the specific fields returned, which is beyond what annotations provide. No contradiction.
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 convey purpose, output, and usage guidance without any wasted words or repetition.
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 read-only tool with one optional parameter and no output schema, the description adequately covers purpose, output fields, and usage 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 coverage is 100% and the parameter description is clear. The description does not add additional meaning beyond the schema, which is sufficient.
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 it lists the caller's active subscriptions and matches the title. Distinguishes from sibling tools like subscribe/unsubscribe by implying it is used for review.
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 guidance on when to use the tool: 'to review what you're monitoring before adding more or to find an id to cancel.' Implicitly suggests not using it when you already have the information, but could be more explicit about 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 have distinct purposes with clear descriptions, but some overlap exists, e.g., ask_pipeworx vs ask_pipeworx_grounded, and several entity/company tools that could be confused. Overall, well-described and mostly disambiguated.
Tool names follow consistent patterns: snake_case, with clear prefixes for each group (e.g., polymarket_*, pipeworx_*, get_article, etc.). Naming is predictable and systematic, making it easy to understand the tool's domain and action.
33 tools is high for a server named 'Devto', where only a few tools actually relate to DEV.to. The majority are for Pipeworx data and Polymarket, which are unrelated. The tool count feels bloated and misaligned with the server's apparent primary purpose.
For the DEV.to domain, coverage is incomplete: lacks create/update/delete for articles and missing user profile management. The Pipeworx and Polymarket tools are extensive, but that doesn't compensate for the gaps in the core feature set implied by the server name.