unsubscribeCancel a subscription by id. Ownership is enforced — you can only cancel your own subscriptions. The row is deactivated (not deleted) so its historical events stay available via recent_alerts.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Subscription id (uuid) returned by subscribe. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Adds key behavioral context beyond annotations: row is deactivated (not deleted), history preserved via recent_alerts. This explains side effects and data lifecycle.
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 focused sentences, front-loaded with action, no redundant words. Every sentence adds value.
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?
Covers action, ownership, and effect on data. Lacks mention of return value, but for a simple idempotent mutation this is minor. Well-rounded overall.
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 the single parameter fully (id as uuid from subscribe). Description adds little beyond 'by id', but ownership enforcement indirectly relates. Baseline 3 due to 100% coverage.
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?
Describes canceling a subscription by id, clearly distinguishing from sibling tools like subscribe and list_subscriptions. Verb 'Cancel' and resource 'subscription' are specific and unambiguous.
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?
States ownership enforcement (only your own subscriptions). Clear context for use, though lacks explicit when-not-to-use or comparison to alternatives. Still strong guidance.
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.