Get ZoomInfo Org Chart

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

Annotations already confirm read-only, idempotent behavior. The description adds the prerequisite workflow (search company first) and describes the output structure (hierarchical list of contacts with titles, departments, management levels). It does not disclose limitations like pagination, but given annotations cover safety, this is adequate and slightly above baseline.

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 well-organized: an opening definition, prerequisite note, args list, return summary, and examples. The args list slightly duplicates schema descriptions but the overall structure is efficient and front-loaded.

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?

With no output schema, the description compensates by explaining what the return contains (hierarchical list with titles, departments, management levels) and giving examples. It covers the required company_id, optional department filter, and response_format, making it sufficiently complete for an agent to invoke.

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 input schema has 100% coverage with descriptions for all three parameters. The description reinforces this with an args list and provides concrete examples mapping natural language to parameter values, adding practical value beyond the 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 the tool retrieves an org chart for a company from ZoomInfo, specifying it shows reporting hierarchy, departments, and management levels. It is easily distinguished from sibling tools like zoominfo_search_company (search companies) and zoominfo_get_tech_stack (technology stack).

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 instructs to use zoominfo_search_company first to obtain the company ID, giving a clear prerequisite. It does not, however, contrast with alternative tools or state when not to use this tool, so it is not a perfect 5.

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