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?
Provides rich details beyond annotations: ownership enforcement, soft-delete (deactivation instead of deletion), and retention of historical events via recent_alerts. No contradiction with 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 concise sentences front-load the primary action and immediately add critical behavioral nuance. No unnecessary words.
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 tool with one parameter and no output schema, the description covers purpose, behavior, and side effects. Could mention success/error response, but current information is sufficient.
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 already describes the id parameter as 'Subscription id (uuid) returned by subscribe.' The description adds 'Cancel a subscription by id,' which is helpful but does not significantly enhance semantic understanding beyond the schema.
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 the action (cancel), resource (subscription by id), and distinguishes from sibling tools like subscribe and list_subscriptions by noting ownership enforcement and soft-deletion behavior.
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?
Describes when to use (cancel subscription) and a constraint (ownership enforced). Lacks explicit 'when not to use' or alternatives, but context is clear given sibling tool names.
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, e.g., Amazon and Walmart tools are platform-specific. A few overlapping tools like ask_pipeworx, ask_pipeworx_grounded, and deep_research are differentiated by clear usage guidance, so an agent can disambiguate with reasonable effort.
Tool names mix verbs and nouns with varying styles (e.g., ai_visibility_check, compare_entities, scan_competitor_ai_presence). There is no uniform pattern like verb_noun; some are descriptive phrases. The inconsistency is noticeable but not chaotic.
36 tools is too many for a server named 'Traject Ecommerce', as many tools cover unrelated domains (Polymarket, npm packages, SEC filings). The scope is excessively broad, making the server feel like a general-purpose plugin rather than a focused ecommerce toolset.
For an ecommerce-focused server, it only covers Amazon and Walmart product/search/reviews, missing major platforms and backend operations. The broader tool set is detailed but not ecommerce-specific, leaving obvious gaps for the intended purpose.