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 value beyond annotations: explains row is deactivated, not deleted, and historical events stay available. 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 compact sentences, no superfluous text. First sentence states action, second adds important behavioral nuance.
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?
With one parameter, no output schema, and comprehensive annotations, the description covers all necessary context: action, constraints, side effects.
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 already fully describes the id parameter (100% coverage). Description does not add new parameter information beyond what is in 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?
Clear verb+resource: 'Cancel a subscription by id.' Distinct from sibling tools 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?
States ownership enforcement: 'you can only cancel your own subscriptions.' Provides clear condition for use but no explicit alternative 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 distinct purposes, but some overlapping function sets (e.g., multiple Polymarket tools, multiple ask/research tools) could cause confusion. However, descriptions are detailed enough to differentiate.
Naming is mostly consistent with snake_case and verb+noun patterns, but a few tools start with nouns (polymarket_*, pipeworx_*), creating minor inconsistency.
At 32 tools, the server feels heavy and covers many disparate domains. While each tool has its place, the high count strains coherence.
Given the server name 'Rentcast', only two tools relate to rental data. The rest cover unrelated domains, leaving a major gap for the intended primary purpose.