sync_lead_list

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'Sync' implies data mutation, but the description doesn't state whether this overwrites or merges existing local leads, whether it deletes local records not in the Hunter list, requires authentication state, or has rate limits. For a mutating sync operation with zero annotation coverage, this is a significant gap.

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 a single efficient sentence that communicates the core action with no waste. It's appropriately sized for a single-parameter tool, though one could argue it's under-specified rather than concise—but given the simple schema, the brevity is reasonable.

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?

This is a mutating sync operation with no annotations and no output schema, so the description must compensate. It doesn't disclose what 'sync' entails (merge vs. replace, upsert semantics), the effect on existing local records, authentication prerequisites, or what the function returns. For a data-modifying operation with full behavioral disclosure burden, this is incomplete.

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 schema has 100% description coverage for the single parameter (listId, described as 'Hunter.io list ID (integer as string)'). The description adds no parameter details beyond what the schema already states, so with full schema coverage, the baseline of 3 is appropriate. No additional format validation, defaults, or examples are provided beyond the schema.

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 states a clear purpose: 'Sync a Hunter.io lead list into local lead records.' It specifies the verb (sync), the resource (Hunter.io lead list), and the target (local lead records). It doesn't explicitly distinguish from siblings like list_leads or list_lead_lists, but the 'sync' action is clearly different from listing operations.

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?

No when-to-use guidance is provided. The description doesn't mention prerequisites (e.g., having an existing Hunter.io list), when this is appropriate versus list_leads or list_lead_lists, or any caveats about syncing behavior such as idempotency or whether it replaces or merges existing records.

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