import_contacts

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

No annotations are provided, so the description carries the burden of behavioral disclosure. It mentions CSV import and tag application but does not clarify error handling, idempotency, rate limits, or authentication details beyond the apiKey parameter. The updateExisting behavior is implied but not elaborated.

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?

Two sentences, no fluff. Every sentence provides essential information: the action and format, then the minimum requirements and optional tags. Highly concise and well-structured.

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 4 parameters, no output schema, and no annotations, the description covers the core functionality but misses details like return value, batch limits, or error behavior. It is adequate for a simple import tool but not thoroughly 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?

Schema description coverage is 100%, so baseline is 3. The description adds value by clarifying that each CSV row must have an email column and that tags apply to all imported contacts, which goes beyond the schema's parameter descriptions. However, it does not explain the CSV format in detail beyond what the schema provides.

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 action ('Bulk import'), the resource ('contacts'), and the data format ('CSV data'). It also specifies the minimum requirement (email column) and the ability to apply tags, making the tool's purpose distinct from sibling tools like create_contact (single contact) or add_contacts_to_audience (add to audience).

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 implies usage for bulk imports but does not explicitly contrast with other contact-related tools (e.g., create_contact for single contacts, add_contacts_to_audience for adding to audiences). It lacks when-to-use or when-not-to-use guidance, relying on the user to infer from the sibling list.

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