crm_sync

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already indicate write and destructive capabilities (readOnlyHint false, destructiveHint true), so the description's job is to add context. It does: it mentions 'Tracks sync status to avoid duplicates' (implying idempotency), 'Includes conversation history as notes' (additional side effect), and 'The key is saved for future syncs' (a persistent side effect). These go beyond the raw annotations, providing valuable behavioral disclosure without contradicting them.

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 moderately lengthy but every sentence adds necessary information: purpose, behavior, setup instructions, and parameter details. The main action is front-loaded, followed by a structured args section. While slightly verbose, it is efficient and not tautological. It earns a 4 for clarity despite not being ultra-terse.

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 description covers all essentials for an agent to call the tool: what it does, when to use it (CRM integration, pipeline sync, lead handoff), how to set up (public app token), and what each parameter means. Since an output schema exists, it need not describe return values. The only minor gap is not mentioning potential side effects on existing HubSpot data (e.g., whether re-syncing updates or overwrites), but the 'avoid duplicates' note partially covers this. Overall, it is complete enough for correct 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%, so the description carries the full burden. It explains each parameter: campaign_id (defaults to most recent), filter (with 'won' default and enumerated options 'hot_leads' and 'all'), and hubspot_api_key (optional, only needed first use, saved). This exceeds the schema's bare defaults and types, giving the agent actionable semantics for invoking the tool correctly.

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 verb 'Sync' and the resource: 'campaign contacts and deals to HubSpot CRM'. It goes further to specify the types of data pushed ('won deals, hot leads, or all contacts') and the target ('as contacts + deals'). This distinguishes it from sibling tools that might handle other CRM or messaging functions. The purpose is unambiguous and specific.

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 clear context on when to use: for CRM integration, deal pipeline sync, and lead handoff to sales teams. It gives setup prerequisites and specifies that the API key is only needed on first use. However, it does not explicitly name alternative tools or state when not to use this tool, which would be needed for a 5. It implies usage rather than contrasting with alternatives, so a 4 is appropriate.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.