Bulk-create contacts

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

The description adds meaningful behavioral context beyond the annotations by disclosing the 1000-contact batch limit, the 3-calls-per-minute rate limit, and the per-contact requirement of email or phoneNumber. It does not discuss idempotency or partial-failure behavior, but the provided details are valuable.

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 three short sentences with no filler. It front-loads the primary purpose and then adds essential constraints, with every sentence contributing useful 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?

Given the output schema exists and the structured schema defines the fields, the description provides enough information to invoke the tool correctly: required contact info, batch size, and rate limit. Minor gaps remain around failure semantics and deduplication, but they do not block correct use.

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 0% description coverage, so the description must compensate. It does by stating that each contact in the array must have email or phoneNumber, a critical constraint not encoded in the JSON schema. It also summarizes the batch size limit, adding value beyond the parameter names.

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 opens with 'Create many contacts in one import', which names a specific verb, resource, and mode. This clearly differentiates it from the sibling create_contact tool, which handles single contact creation.

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 gives clear context for when to use this tool: when many contacts need to be created in a single import. It also mentions constraints, but it does not explicitly name alternatives like create_contact or state when not to use this tool.

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