import_contacts_txt

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

No annotations are provided, so the description carries the full burden. It only notes that this is a mutation via '[mutation]', but does not disclose any behavioral traits such as whether it appends or overwrites contacts, required permissions, error handling, or side effects.

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-structured line with a dash separator. It is front-loaded with the action and resource, contains no redundant words, and is easy to read.

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 parameters, no output schema), the description provides the core purpose and a minor file format detail. However, it lacks completeness on expected behavior (e.g., duplicate handling, validation, or success/error output). For a simple tool, it is somewhat adequate but not fully informative.

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 input schema covers both parameters with descriptions. The description adds minimal extra meaning by specifying 'one phone per line', clarifying the file format beyond the schema's 'Archivo TXT a importar'. However, this is a minor addition; the schema already covers the essence.

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 action (import contacts), the resource (from a text file to a marketing list), and the format (one phone per line). It distinguishes itself from the sibling tool import_contacts_csv by specifying 'text file' rather than 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 provides no guidance on when to use this tool versus alternatives like import_contacts_csv or import_contacts_manual. There is no mention of prerequisites, limitations, or context such as 'use for plain text files only'.

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