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?
Beyond annotations, the description reveals that the row is deactivated (not deleted) and that historical events remain via recent_alerts. This adds significant behavioral context not present in annotations.
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: first states the action, second covers ownership and effect. No wasted words, front-loaded with core purpose.
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 description covers purpose, usage condition, and behavioral effect. It references a sibling tool (recent_alerts). However, it omits the return value or success confirmation, which is a minor gap for a simple mutation.
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%, so the schema already documents the 'id' parameter fully. The description offers no additional parameter semantics, maintaining the baseline for high 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?
The description clearly states 'Cancel a subscription by id,' with a specific verb and resource. It distinguishes from sibling tools like subscribe (creates) and list_subscriptions (lists) by specifying the action and effect.
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 explicitly states ownership enforcement ('you can only cancel your own subscriptions'), providing clear context on when to use it. It does not explicitly mention alternatives, but the restriction is clearly communicated.
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.
The set mixes Codeforces-specific tools with a large Pipeworx data toolkit. Within the Pipeworx family, ask_pipeworx, ask_pipeworx_beta, and ask_pipeworx_grounded are nearly identical (the beta explicitly matches the stable version today), and deep_research/discover_tools/suggest_questions also overlap as meta entry points, creating real selection hazard. An agent could easily misselect among these.
Naming patterns are mixed: some tools use verb_noun (list_subscriptions, validate_claim, resolve_entity), some use bare verbs (remember, forget, recall), and some are noun phrases (problemset, blog_entry_view, recent_actions). Word order also varies (contest_list vs list_subscriptions), so no consistent convention is followed.
39 tools is far too many for a server named 'Codeforces' — only 8 tools actually concern Codeforces, while the remaining 31 are unrelated Pipeworx/utility tools. This bloats the surface and makes the server feel unfocused, especially for an agent expecting a compact Codeforces API.
For the Codeforces domain, the core read-only API is covered (contests, standings, problems, user info/rating/status, blog entries, recent actions) but some endpoints are missing (blog comments, rated list, problem statements). The large number of extra tools does not fill these gaps and instead obscures the intended purpose.