import_contacts

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

No annotations provided, so description bears full burden. Discloses basic import behavior but omits critical details like what happens on duplicate emails (updateExisting param is there but not explained), error handling, validation, or side effects. Does not mention if it creates contacts or updates existing.

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?

Extremely concise: two sentences covering the main purpose and a key requirement. No filler or repetition. Front-loaded with the core action.

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?

Lacks output schema and does not describe return value or success indicators. For an import tool, agents need to know what the response looks like (e.g., count imported, errors). Missing behavioral details like validation and error handling.

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 covers all 4 parameters with descriptions (100% coverage). Description adds context that CSV must have email column and tags can be applied, which partially overlaps with schema. Adds marginal value beyond schema.

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?

Clearly states the action (bulk import), resource (contacts from CSV data), and a key requirement (minimum email column). Distinguishes from siblings like create_contact (single) and add_contacts_to_audience (adding to audience).

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?

Implies usage when you have CSV data to import, but lacks explicit when-to-use vs alternatives, prerequisites (e.g., need Send16 API key), or exclusions. Does not guide 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.