contacts_import_csv

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

The description discloses key behaviors: upsert by email and optional deletion of name-only duplicates. Without annotations, this adds meaningful context beyond the schema, though details on error handling or permission requirements are missing.

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 extremely concise with two short sentences that cover the essential purpose and a key behavioral option. No extraneous 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?

The description covers the main operation and a key behavioral aspect but lacks information about return values, error handling, or other contextual details. Given no output schema, it could be more complete.

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%, so the schema already explains each parameter well. The description does not add significant new meaning beyond what the schema provides.

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 'Import contacts from a Google Contacts CSV export', specifying a specific verb and resource. It distinguishes from sibling tools like contacts_create (single) and contacts_update by focusing on bulk import from CSV.

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 implies usage for CSV import but does not explicitly state when to use this tool versus alternative contact creation tools. No guidance on prerequisites or when not to use it is provided.

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