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

readOnlyHint=true already tells the agent this is a safe, non-mutating call, so the description's burden is lighter. It adds the '1:1 match' semantics and the API endpoint, but does not say what happens on a miss, how confidence gating affects results, or whether person data is dropped when unavailable.

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?

Two tightly written sentences with no padding; the value proposition is front-loaded and the endpoint reference trails it. Every clause carries information.

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 and five parameters, the description carries more return-value burden than usual, and it does enumerate the main returned entities (location, company, optional person). It omits pagination/shape details, but for a read-only enrichment endpoint that is a minor 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 description coverage is 100%, so all five parameters are already fully documented, which sets the baseline at 3. The description only reinforces one parameter implicitly ('optionally associated person data' for return_person) and adds no new syntax, format, or behavior detail 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?

States a specific verb (enrich) and resource (IP address) and names the returned fields: location, company, and optionally associated person data. It also pins the lookup mechanism ('1:1 match against PDL's IP dataset'), which separates it conceptually from the sibling person/company enrichment tools, though it never names an alternative explicitly.

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?

Usage is only implied: the agent infers this is the tool for IP-based enrichment because the resource is an IP. There is no statement of when to prefer it over pdl_person_enrich or pdl_company_enrich, nor any exclusion or prerequisite guidance.

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