ZoomInfo company profile

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

With no annotations, the description carries the transparency burden. It mentions the output is 'structured data', hinting at a normalized format, but does not disclose behavior like handling invalid URLs, rate limits, or whether it scrapes live data. For a read-only lookup, this is acceptable but not rich. The lack of any caveats is a minor gap.

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 a single concise sentence that names the resource and key data points. It is efficient and easy to scan, though it is terse and could have added usage context without bloating.

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?

The tool is simple (one parameter, no output schema), so the description is mostly adequate. It lists common data categories but does not guarantee the full return structure or mention any limitations. For a tool with no output schema, more detail would be beneficial, but the minimalism is not critically incomplete.

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 already provides 100% coverage for the single parameter (url) with a clear description. The text adds nothing about parameters themselves, but it implicitly relates the URL to the output data. Since schema coverage is high, baseline 3 is appropriate.

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 explicitly states the tool provides structured ZoomInfo company data, listing key fields (employees, revenue, technologies, contacts). This is clear and specific enough to infer it retrieves company profiles. It does not explicitly differentiate from siblings like LinkedIn or Crunchbase company profiles, but the name and data categories provide reasonable context.

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?

No guidance is given on when to use this tool versus alternatives. The description does not mention prerequisites, when it is appropriate (e.g., need ZoomInfo-specific data), or when to choose other company-data tools. The agent is left without explicit usage criteria.

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