Create Contacts (Bulk)

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

No annotations are provided, so the description must carry the full burden. It only says 'Create multiple contacts for a profile' and lacks any disclosure of behavioral traits such as whether the profile must exist, how duplicates are handled, partial failure behavior, or authentication needs. This is insufficient for a mutating tool.

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 short sentence that is front-loaded with the verb and resource. Every word earns its place, and there is no redundancy or filler.

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?

With no annotations and no output schema, the description is too thin to be complete. It does not explain the relationship to reach_contacts_create, bulk size limits, return behavior, or failure modes. While the schema handles parameter coverage, the overall tool context is underdeveloped.

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%, with all parameters (profile_uuid, contacts array, email, first_name, last_name) already described. The description adds no extra meaning beyond what the schema provides, so the baseline of 3 applies.

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 'Create multiple contacts for a profile' with a specific verb (create), resource (contacts), and scope (multiple, for a profile). It distinguishes from the sibling reach_contacts_create by explicitly saying 'multiple', though the sibling name already implies the single variant.

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?

Usage is implied for bulk creation based on the name and description, but there is no explicit when-to-use guidance, exclusions, or mention of the alternative reach_contacts_create. The bulk vs. single distinction is carried by the title and name, not the description.

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