bulk_import_contacts

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

The description explicitly states 'Not idempotent — calling twice may create duplicates', which aligns with the idempotentHint=false annotation. It also labels the operation as a write ('🟡 WRITE · creates data'). No contradictions with annotations. Adds value beyond annotations by clarifying duplicate risk.

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 concise (2-3 lines) and front-loaded with the purpose. However, it includes redundant formatting (emojis, HTTP path) that could be merged. Still, every sentence contributes directly to understanding.

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 complexity (nested objects, callback, batching limits), the description is minimal. It does not mention batching behavior, callback details, or error handling. However, the input schema is richly detailed, partially compensating. Could provide more high-level context.

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 main description does not add any parameter semantics beyond what the input schema already provides. Since schema description coverage is 100% for all nested properties, the description does not need to compensate. Baseline 3 is appropriate.

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' with a verb ('Import') and resource ('contacts'). It distinguishes itself from siblings like 'create_a_new_contact' by implying bulk operation. The mention of HTTP method and endpoint adds further clarity.

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 does not explicitly state when to use this tool vs alternatives. However, the input schema mentions a minimum of 10 contacts, directing users to contact/sync for fewer. No explicit when-to-use or when-not-to-use guidance is provided in the main description.

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