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 behavioral detail beyond annotations: ownership check, deactivation rather than deletion, and historical data preserved. Aligns with idempotentHint=true and destructiveHint=false. No contradiction.
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. Every sentence adds unique value (ownership, deactivation, historical data). No wasted 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 with 1 parameter and no output schema. Covers purpose, ownership, effect, and links to recent_alerts for historical context.
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 parameters with description for 'id'. Description does not add parameter-specific meaning beyond schema, but no gap exists. Baseline 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?
Describes specific verb 'Cancel' and resource 'subscription by id'. Clearly distinguishes from sibling tools like 'subscribe' and 'list_subscriptions' by mentioning ownership enforcement and deactivation 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?
States ownership enforcement ('only cancel your own subscriptions'), which provides clear when-to-use guidance. Implicitly excludes canceling others' subscriptions. Lacks explicit 'when not to use' but adequate.
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.
Some tools have overlapping purposes (e.g., ask_pipeworx and ask_pipeworx_grounded; multiple Polymarket analysis tools) but descriptions help differentiate. Odoo-specific tools are distinct among themselves but muddled with many general-purpose tools.
Naming is heavily inconsistent: Odoo tools follow 'odoo_list_*' pattern while others use varied structures like verb-first (forget, remember) or noun-first (entity_profile, recent_alerts). No unified verb_noun pattern across the set.
At 32 tools, the server exceeds the typical well-scoped range (3–15) but is not excessively large. Many tools are generic and could be trimmed, making the set feel heavier than necessary.
Despite many tools, the server lacks essential CRUD operations for Odoo (e.g., create/update/delete leads) and the 'Odoo' name misrepresents the actual focus. Gaps in Odoo functionality and mixed domains create a sense of incompleteness.