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 readOnly, idempotent, non-destructive nature. Description adds value by listing the exact fields returned (id, type, params, etc.) and noting the optional include_inactive parameter, enhancing transparency.
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, each serving a distinct purpose: stating the function and providing usage guidance. No redundant or extraneous content.
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, the description adequately covers returned fields. Annotations cover safety. Some may want pagination info, but for a small list it's acceptable. Lacks only minor details like ordering.
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 for the single parameter. Description adds minimal extra meaning beyond what the schema already provides (just implies default of active subscriptions). 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?
Description clearly states it lists the caller's active subscriptions with a specific verb and resource. While it doesn't explicitly distinguish from other list tools in the sibling list, the context of subscriptions makes it clear.
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 guidance on when to use the tool: before adding more subscriptions or to find an id to cancel. Does not name alternatives but implicitly differentiates from subscribe/unsubscribe.
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 clearly distinct purposes, but there is some overlap between research-oriented tools like ask_pipeworx and deep_research, and between entity_profile and compare_entities. Descriptions help differentiate them, so overall an agent can tell them apart.
Tool names are inconsistent, mixing snake_case (ask_pipeworx, list_subscriptions) and camelCase (bag_research, compare_entities). There is no uniform naming pattern, which can be confusing.
With 35 tools, the set is too large for a server named 'Mastodon'. Only a few tools are actually Mastodon-related (e.g., get_account, get_timeline), while the majority are PipeWorx tools unrelated to the core purpose.
As a Mastodon server, the toolset is severely incomplete: it lacks basic social media operations like posting statuses, following/unfollowing, and engaging with content. The name misrepresents the actual capabilities.