Import many leads

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

Beyond the annotations (which only deny read-only/idempotent/destructive), it discloses partial-success semantics, per-row validation, error indexing, the failed_count result field, and the required leads:write scope. This is substantial and operationally useful behavioral context for a write operation.

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 focused sentences deliver purpose, partial-failure behavior, result guidance, and authentication requirements. Every sentence earns its place with 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 batch mutation with no output schema, it covers limits, validation outcomes, error reporting, where to look for failures, and required auth scope. An agent has enough to call it correctly and interpret the response.

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?

With schema description coverage reported at 0%, the description needed to clarify the lead object fields, yet it only says 'rows' and effectively repeats the 1,000 cap already present in maxItems. It adds no meaningful explanation of name, phone_number, tags, or fields beyond what the schema structure already shows.

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 states a specific verb and resource ('Create up to 1,000 leads in one request') and the batch capacity makes it clearly distinct from the singular create_lead sibling. The title 'Import many leads' reinforces the same purpose without ambiguity.

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 batch context is implied by 'up to 1,000 leads in one request', but the description never explicitly says when to choose import_leads over create_lead or another sibling. It leaves the routing decision to inference rather than naming an alternative or exclusion.

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