import_mapped_contacts

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

No annotations are provided. The description includes '[mutation]' and 'importa' indicating a write operation, but lacks details on duplicate handling, limits, or side effects. With no annotations, the description should offer more behavioral context.

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, consisting of a title-like phrase and a single sentence. It wastes no words, though structured formatting could improve scannability.

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 basic process and parameters but omits return value, error handling, and prerequisites (e.g., needing a previewed file). For a mutation tool with no output schema and no annotations, more detail is warranted.

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 coverage is 100%. The description merely echoes the schema's purpose (specifying phone and name columns) without adding new meaning or constraints beyond the field descriptions.

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 tool imports contacts with column mapping from a previewed CSV file, specifying phone and name columns. This distinguishes it from sibling import tools like import_contacts_csv (simpler import) and import_contacts_manual (manual entry).

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 the file must be previewed first and that the user specifies column indices, but it does not explicitly state when to use this tool over alternatives or provide exclusions.

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