import_contacts_csv

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 of behavioral disclosure. While [mutation] indicates state change, it fails to specify what happens during import (e.g., duplicate handling, overwrite vs. append, validation). Crucial behavioral traits like authorization needs or rollback behavior are absent.

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, well-front-loaded sentence with a useful tag. Every word earns its place, and there is no redundancy. It efficiently conveys the core purpose.

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 tool's simplicity (2 params, no output schema), the description is minimally viable. However, it omits important context like return value (success indicator) and file constraints (e.g., max size, character encoding). With many sibling tools, additional differentiation would improve completeness.

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?

Input schema has 100% description coverage, so parameters are already well-documented. The description adds no additional semantic value beyond the schema, such as clarifying the file's required structure or format. 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 the verb 'importar' (import), the resource 'contactos desde CSV' (contacts from CSV), and the destination 'a una lista de marketing' (to a marketing list). The [mutation] tag further clarifies the action type, distinguishing it from read-only tools. This specificity effectively differentiates it from siblings like import_contacts_txt.

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 provides no guidance on when to use this tool versus alternatives. It does not mention prerequisites, file format requirements (e.g., encoding), or edge cases. With many sibling import tools (e.g., import_contacts_manual, import_contacts_from_conversations), the lack of usage direction is a significant gap.

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