sdr_regenerate_searchRe-run Claude on the agent's current knowledge to regenerate the entire ICP profile and hunter configuration. Useful after the agent's script changed significantly.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden. It does disclose that the tool re-runs Claude and regenerates the entire profile, implying a potentially destructive overwrite. However, it does not state whether this replaces existing data, what prerequisites exist, or whether there are side effects beyond regeneration.
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 core action is front-loaded, and the usage hint is additive rather than redundant.
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?
The tool has one required parameter and no output schema, yet the description omits what the id represents, whether the target search must already exist, and what the agent should expect after invocation. This is too incomplete for reliable tool selection and invocation.
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 description coverage is 0% and the description never mentions the single 'id' parameter. The agent receives no guidance on what id refers to or how to obtain it, which is a significant gap for a required parameter.
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 identifies the verb ('re-run Claude') and the resource ('entire ICP profile and hunter configuration'), making it obvious this tool regenerates rather than creates or updates. The phrase 'regenerate' also distinguishes it from create/update siblings, though it does not explicitly name them.
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 provides a concrete trigger condition: 'Useful after the agent's script changed significantly.' This gives clear context for when to use the tool, though it does not mention any exclusions or alternative tools.
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.
Despite consistently detailed descriptions, several tool pairs have unclear boundaries: `get_subscription_limits` and `get_agent_plan_limits` describe essentially the same agent-slot check, `crm_get_conversation` and `crm_communication_thread` both claim to return the full message thread, and `get_credit_usage_by_agent` vs `get_credit_usage_for_agent` differ only by preposition. At 149 tools, an agent will regularly misselect between these near-duplicates.
The dominant pattern is verb_noun with domain prefixes (`crm_*`, `sdr_*`) and a consistent `preview_*` family that maps cleanly to destructive/expensive actions. Deviations are minor but real: CRM deletes use the inverted `delete_crm_*` form while other CRM ops use `crm_*`, and credit-usage tools mix `by_agent`/`for_agent` prepositions.
149 tools is nearly three times the 50+ threshold the rubric treats as extreme, even though the platform genuinely spans agents, campaigns, audiences, CRM, SDR, billing, and connections. Many could be consolidated without losing capability — e.g. the 11 balance/credit-usage tools, the two LinkedIn-account listers, and the 15+ preview variants.
The surface is remarkably complete: full CRUD/lifecycle coverage for agents, campaigns, audiences, CRM leads/stages, and SDR searches, plus billing, analytics, and connection management. Destructive or costly operations all have preview/approval counterparts, so there are no dead ends. If anything the risk is over-coverage rather than gaps.