bulk_import_contacts

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

No annotations exist, so the description must carry the full behavioral burden. It fails to disclose important traits: whether existing contacts are updated or skipped, error handling for malformed JSON, rate limits, or the nature of the operation (e.g., destructive or additive). The description is too brief for a bulk-mutation 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 two sentences long, front-loading the core purpose. Every sentence adds necessary detail. 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?

Given no annotations and 3 parameters (0% schema coverage), the description does not adequately explain behavior like duplicate handling, response format (despite output schema existing), or error scenarios. For a data-modifying tool, this is a significant gap.

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 0%, so the description adds value by explaining contacts_json as 'JSON array of {email, first_name, last_name, phone}'. However, list_id and tag_id are only vaguely described as 'optionally add to a list or tag', without clarifying format or relationship. This is helpful but incomplete.

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 'Bulk import contacts' and specifies the JSON array format. This is a specific verb+resource combination. However, it does not explicitly differentiate from single-contact creation tools like create_contact, which is a minor gap given the context of sibling tools.

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 mentions optional addition to a list or tag, providing some usage context. But it gives no guidance on when to choose this tool over alternatives like create_contact (for single contacts), or when not to use it (e.g., for updating existing contacts). No explicit when/when-not guidance.

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