Search ZoomInfo Companies

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior. The description adds value beyond annotations by specifying return fields (employee count, revenue, industry, location, description) and the utility of the returned company ID for subsequent tools. No contradictions with annotations.

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?

Well-structured with an upfront purpose, followed by return details, Args summary, and examples. The Args section is slightly redundant with the schema but front-loads key information. No redundant prose; each section contributes.

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 tool's complexity (10 optional params, no output schema), the description covers search criteria, return types, and follow-up usage. It includes examples and pagination controls. Could mention error handling or default response format, but these are adequately implied by schema annotations.

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 description coverage is 100% and the Args section largely mirrors schema descriptions. However, the description adds practical examples ('Find Acme Corp' -> company_name='Acme') and clarifies relationships like min/max employees as a range, going beyond 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 searches the ZoomInfo database for companies using specific filters (name, domain, industry, size, revenue), returning firmographic data. It distinguishes from siblings like zoominfo_search_contact (people) and zoominfo_get_org_chart/tech_stack (follow-ups) by focusing on company search.

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 gives clear context for when to use this tool: to search companies and obtain company IDs for further ZoomInfo operations. It mentions follow-up tools (zoominfo_get_org_chart, zoominfo_get_tech_stack), but does not explicitly state when not to use it or compare with alternative search tools like clay_enrich_company or linkedin_search_companies.

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