Sync your Salesforce accounts, deals, and contacts into persistent memory so Claude knows your CRM landscape in every future session. Call after any significant Salesforce update.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description must carry behavioral disclosure. It does disclose a key trait: syncing into persistent memory for future sessions. However, it does not explain side effects like whether existing memory is overwritten, whether the operation is reversible, or any authorization requirements. This is a meaningful gap for a state-changing tool.
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 with no filler. The first sentence front-loads the core purpose and effect; the second gives a concise usage trigger. Every word earns its place.
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?
Given the tool has no parameters and no output schema, the description covers the what (Salesforce accounts, deals, contacts), where (persistent memory), and when (after significant update). It does not describe the return value or potential errors, but for this simple, no-argument tool the description is largely complete.
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, so the input schema fully covers this dimension. The description adds value by specifying what gets synced (accounts, deals, contacts), but no parameter-level detail is needed. Baseline 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's function: syncing Salesforce accounts, deals, and contacts into persistent memory for future sessions. It uses a specific verb ('sync') and resource ('Salesforce'), and the persistent-memory outcome distinguishes it from sibling tools like get_salesforce, which are read-only lookups.
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 gives explicit guidance on when to call: 'Call after any significant Salesforce update.' It does not mention when not to use it or name alternatives, but the trigger context is clear and sufficient for a tool with no parameters.
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.
Many tools are duplicated across services (e.g., get_inbox vs get_outlook_inbox vs get_unified_inbox; create_calendar_event vs create_outlook_event), causing confusion. Summary tools like catch_me_up, morning_briefing, and weekly_preview overlap significantly in function. The sheer number of similar-sounding tools makes selection error likely.
Names generally follow a verb_noun pattern, but verbs are inconsistent (get, check, lookup, fetch, etc.) and some tools use service-specific prefixes (hubspot_, sf_, qb_) while others do not. Mixed conventions like email_action vs send_email and append_to_doc vs append_to_excel reduce clarity, but the overall pattern is still readable.
107 tools is far beyond the typical scope for a single server, making it difficult for an agent to navigate and choose appropriately. The count feels like a kitchen-sink collection of every possible integration rather than a curated set, severely impacting usability.
The server covers a wide range of domains (email, calendar, contacts, documents, CRM, finance, messaging), but there are notable gaps like no delete for contacts or files, no update for Slack messages, and no way to list all documents. Core workflows exist for most areas, but depth is inconsistent.