Batch Ingest Leads

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

Discloses that duplicates are skipped (not failed) so partial batches succeed, and specifies the return structure with ingested and skipped arrays. This adds significant detail beyond annotations, which only indicate idempotency and non-destructiveness.

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?

Three sentences, all essential: action and limits, behavior on duplicates, and usage guidance. Front-loaded with 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 single parameter and no output schema, the description covers all important aspects: batch size, duplicate handling, return format, and comparison to sibling tool. Nothing missing.

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% with detailed property descriptions. The description adds the response shape and references the sibling tool's schema, which is helpful since no output schema is provided. Baseline is 3, but the added output semantics justify a 4.

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 'Add 1 to 100 leads in a single call,' specifying the action and resource. It distinguishes from sibling tool lead_ingest by mentioning bulk imports and directs users to prefer this over repeated calls.

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?

Explicitly advises 'Prefer this over repeated lead_ingest calls for bulk imports (CSV/webhook drops),' giving clear context on when to use this tool and when to use the alternative.

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