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

With readOnlyHint already covering safety, the description adds useful behavioral disclosure: it returns firmographics or a 404 'no match' body and notes relative reliability of inputs. It does not contradict the read-only annotation.

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?

Four short sentences deliver purpose, prerequisites, return behavior, and endpoint with no filler. The core action is 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?

For an 11-parameter read-only enrichment tool with no output schema, the description covers the essential call contract: input requirement, expected return shape, no-match failure mode, and API method. It could be more explicit about how multiple parameters combine and that pdl_id is also an accepted key.

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 the baseline is 3, but the description adds value by grouping accepted identifiers and ranking their reliability (website/ticker/profile over name). The omission of pdl_id from that identifier list is a minor gap.

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 opens with a specific operation, 'Find the single best-matching company record,' and identifies the resource and endpoint. 'Single best-matching' plus the firmographics return clearly distinguishes this enrichment tool from sibling search/identify tools.

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 gives clear applicable context by requiring a 'non-ambiguous input' and names the preferred identifier types. It does not explicitly state when to prefer pdl_company_search or other siblings, so it stops short of full alternative routing.

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