personBulkLookup

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

With no annotations, the description carries the full burden. It mentions the external API and parameter usage, but does not disclose rate limits, pagination, or what happens if data is missing. The read-only nature is implied by 'look up' but not confirmed.

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?

Extremely concise: two sentences and two bullet points, front-loading the core purpose. Every sentence adds essential value with no redundancy.

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?

Missing crucial context: no mention of return format or output structure, given there is no output schema. Does not differentiate from sibling tools like contactEnrich. For a complex nested schema, this is a significant gap.

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 0%, so the description must compensate. It explains the required combinations for each contact and the reveal flags, but does not detail other fields like contactId, metadata.filterBy, or nested company properties. Adds moderate value beyond the raw schema.

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 it looks up person information from the Lusha API, supporting both single and multiple lookups. The verb 'look up' is specific. However, it does not explicitly differentiate from sibling tools like contactEnrich or contactSearch, though the 'bulk' nature is implied.

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 lists required input combinations (LinkedIn URL, full name+company, or email) and warns against using revealEmails/revealPhones unless requested. This provides clear when-to-use guidance, though it lacks explicit comparison to alternative tools.

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