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

Since no annotations are provided, the description carries the full burden of disclosure. It successfully communicates the import limit (1000 rows), the deduplication mechanism, the update semantics, and the cost ('No credits').

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 highly concise, fitting complex operational logic (limit, deduplication, update behavior, cost) into three dense sentences without filler. The information is front-loaded and easy to scan.

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 lack of annotations and the complexity of bulk lead processing, the description is extremely complete. It addresses failure modes (skipped/updated/created reasons) and limitations (1000 row limit) that the structured fields do not capture.

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 schema coverage is only 50%, and the description primarily lists the field names without adding semantic context to the majority of the nine input fields. While it mentions the target 'pipelines (entry stage)', the parameter details remain largely reliant on the schema alone, meeting the baseline but not exceeding it significantly.

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 purpose is clearly stated: 'Import up to 1000 parsed rows as leads into the chosen pipelines (entry stage).' This specific phrasing distinguishes it from single-lead creation tools.

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 explicitly details the deduplication strategy ('Dedup by email/phone') and the critical update logic ('blank fields filled (never overwritten)'), which serves as a vital guideline for how the agent should expect the data to behave during execution.

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