import_contacts_batch

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

With no annotations provided, the description carries the behavioral disclosure burden. It does disclose the upsert-by-email behavior, the maximum batch size, and the accepted contact fields, but it does not mention error handling, partial failures, auth requirements, or what the response contains.

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 compact sentences convey the endpoint, operation, upsert behavior, batch limit, and contact schema with no filler. Key constraints are front-loaded and every clause adds information.

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 is adequate for a basic bulk-import call, covering the essential operation, payload shape, and limits. However, with no output schema, it does not explain expected return values, batch error behavior, or duplicate-within-batch handling, which an agent may need to interpret the result.

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 input schema already documents all three parameters with 100% coverage, so the baseline is 3. The description adds value by specifying the per-contact object shape (email, first_name?, last_name?, unsubscribed?, properties?), which is absent from the schema's generic array item definition.

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 operation: bulk-import contacts from a JSON array, and includes the endpoint and key semantics (upsert by email). It implicitly differentiates from CSV/sheet import siblings by specifying JSON format, though it does not name an alternative explicitly.

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 usage context is implied: use this tool for bulk JSON imports, with a 10,000-per-call limit. However, there is no explicit guidance about when to prefer import_contacts_csv, import_sheet_contacts, or create_contact, nor any when-not-to-use conditions.

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