Open a page to manage push notification subscriptions in your browser. Enables/disables web push notifications for birthday reminders and other alerts.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden. It discloses that the tool opens a browser page and enables/disables web push notifications, which is useful. However, it does not mention whether this is a direct mutation or requires user interaction, nor does it address prerequisites like browser availability. The behavior is partially transparent but not fully detailed.
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?
The description is two sentences, immediately front-loaded with the action ('Open a page'), and contains no redundant information. Every word adds value, and it does not repeat tool name or schema details.
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, parameterless UI-tool with no output schema, the description is largely complete: it states what happens (opens page) and the purpose (manage subscriptions). It could mention limitations (e.g., requires a browser or user interaction), but given the low complexity and absence of output schema, the description covers the essential context sufficiently. A score of 4 reflects minor gaps in behavioral detail.
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?
The tool has zero parameters and the schema coverage is 100% (no properties). The description does not need to add parameter details. It does mention the scope ('birthday reminders and other alerts'), which adds context beyond the empty schema, so a baseline of 4 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?
The description clearly states the tool opens a page to manage push notification subscriptions, with a specific verb ('Open'), resource ('push notification subscriptions'), and scope ('birthday reminders and other alerts'). This distinguishes it from sibling tools like notification_list or notification_create, which handle individual notifications rather than subscription preferences.
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 implies usage for managing web push notification subscriptions but does not explicitly state when to use this tool versus alternatives like notification_list or manage_settings. No exclusions or comparative guidance is provided, making the context clear but leaving the decision to the agent.
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 are clearly distinct by entity, but contact_get and contact_timeline overlap significantly, and debt_manage's action='list' duplicates what other entities do with a dedicated list tool. Descriptions are detailed enough to resolve most ambiguity, though.
Tool names are mostly snake_case and readable, but they mix conventions: noun_verb (contact_create), verb_noun (batch_create_activities), and descriptive phrases (contacts_needing_attention). The noun_manage pattern is dominant, but the lack of uniformity makes the naming less predictable.
With 42 tools, the surface is very large, even for a full-featured CRM. Many tools bundle multiple actions, but the sheer number forces an agent to consider many options, increasing selection difficulty and cognitive load.
The server provides comprehensive CRM coverage: contacts, activities, notes, tasks, reminders, gifts, debts, relationships, tags, custom fields, notifications, settings, and exports. It supports batch operations, duplicate detection, merge, and special queries, leaving few if any obvious gaps.