sync_lead_list

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

The description adds substantial behavioral detail beyond annotations: it writes local records, re-syncing refreshes rather than duplicates, requires an API key and connected account, and has no credit cost. It fully supports the idempotentHint and openWorldHint annotations without contradiction.

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 well-structured and front-loaded with the core purpose. Every sentence provides useful context: workflow position, effects, repeat-safety, prerequisites, and cost implications. No filler or redundancy.

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 what the tool does, why it is needed, the preconditions, side effects, idempotency, and billing implications. With a simple single-parameter schema and no output schema, this is complete enough for an agent to select and invoke it correctly.

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 single parameter listId is already fully described in the input schema with 100% coverage. The description does not add meaningful parameter-specific semantics, which is acceptable given the schema already handles it.

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?

Description states a specific action ('Import a Hunter.io lead list into local lead records') with a clear resource and effect. It also distinguishes from sibling tools like create_lead_list and list_lead_lists by explaining the sync relationship.

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 explicitly says when to run it ('after create_lead_list, or on any existing list from list_lead_lists') and explains why it is necessary ('Until a list is synced its contacts are invisible'). This gives the agent clear workflow context.

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