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

With annotations already declaring write, open-world, non-idempotent, and non-destructive behavior, the description adds substantial context: the operation runs in the background, returns a job id for get_bulk_add_status, skips existing people, and consumes one lookup credit per person for whom an e-mail is found.

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 four dense sentences, front-loads the core action and scope, and includes only operational details that help an agent call the tool correctly.

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?

An output schema exists, so return values need not be explained in detail. The description still covers the key operational facts an agent needs: limit, required profile_url provenance, background job id, duplicate skipping, and credit usage.

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 parameter documentation is already strong. The description adds meaningful semantics for profile_url provenance and refusal rules, the 100-person limit, and credit implications tied to email lookup, though it does not further explain tags, include_phone, or only_with_email beyond their schema 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 names a specific verb and resource ('Add up to 100 people to the customer's connected CRM'), states it runs in the background, and explicitly distinguishes this bulk tool from the single-person sibling add_person_to_crm.

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 clearly routes usage: profile_url must come from search_prospects or find_contact_details, other links are refused, and add_person_to_crm is named as the alternative for one person from any profile link. It also states that existing CRM people are skipped.

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