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 information beyond annotations: ownership enforcement, deactivation vs deletion, and relation to recent_alerts. Annotations already indicate idempotent and non-destructive, so description complements well.
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, front-loaded with purpose, 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?
Complete for a simple tool: explains behavior (deactivation), ownership, and connection to recent_alerts. No output schema needed as return value is implied.
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 100% of the single parameter with description. The description does not add further detail about the parameter beyond what the schema provides, meeting baseline.
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 the verb 'Cancel' and the resource 'subscription by id', distinguishing it from siblings like 'subscribe' and 'list_subscriptions'.
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?
Explicitly mentions ownership enforcement and that the row is deactivated not deleted, providing context for when to use and what happens after. Lacks mention of alternatives but is clear enough.
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.
Multiple tools have overlapping purposes, such as ask_pipeworx and ask_pipeworx_grounded, or bet_research and polymarket_edges. The mix of CRM, data, and betting tools creates confusion about which tool to use for a given task.
Tool names are inconsistent, mixing snake_case (ai_visibility_check, ask_pipeworx) with prefixed names (leadconnector_*) and no clear pattern. Some names are vague (forget, remember) while others are specific.
With 32 tools, the set feels overstuffed for a server named 'Leadconnector'. Many tools are unrelated to CRM (e.g., Polymarket, Pipeworx), and the CRM subset is too small to justify the count.
For the Leadconnector CRM domain, only basic read operations are provided; missing create, update, delete for contacts, campaigns, and opportunities. The non-CRM tools are comprehensive but don't match the server's name.