conduyt_import_deals

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

With no annotations, the description carries the full burden and does so well: it states the tool is side-effect-free by design, intentionally suppresses deal-created automations/webhooks/SMS/email, deduplicates on title + pipeline + contact, requires an owner/admin key, and returns created/skipped/duplicate counts plus per-row errors.

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 front-loaded, dense, and every sentence contributes: purpose, resolution rules, deduplication, side-effect behavior, auth requirement, and return values. There is no filler.

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?

For a complex bulk import with a nested array, no output schema, and no annotations, the description supplies the key operational details an agent needs: prerequisites, resolution behavior, deduplication, side-effect suppression, auth, and error reporting.

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%, so the nested deal fields are already documented. The description adds useful context about name/email resolution and the deduplication key, but most of that overlaps with schema descriptions or describes bulk behavior rather than individual parameter meaning.

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 opens with a specific verb and resource: 'Bulk-import deals from a list of rows in one call.' That immediately distinguishes it from single-deal creation and general update tools, and the phrase 'canonical import engine' signals a dedicated bulk import path.

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?

It gives clear prerequisites — create pipelines first, contacts must exist by email, owner/admin API key required — and implies bulk usage over single-deal creation. It does not explicitly name sibling alternatives such as conduyt_create_deal or conduyt_import_preflight, so it stops short of full when/when-not guidance.

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