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

With no annotations, the description carries the behavioral transparency burden. It does add useful details: free input preflight, provider attribution, likelihood, limitations, signed receipt, and a price of 0.006 USDC. However, it does not disclose authentication needs, side effects, rate limits, or what the returned evidence/receipt structurally contains.

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 sentence with no filler words, and it front-loads the core purpose before listing notable features and cost. It is appropriately brief, though the semicolon-joined feature list reads a bit densely.

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 has 28 parameters, no output schema, and no annotations, so the description is severely insufficient. It does not explain how to construct a valid request, what fields are meaningful together, what the signed receipt looks like, or how preflight and validation behave. An agent would be guessing on most operational details.

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 only 7% across 28 parameters, and the tool description does not compensate. It mentions 'person' and 'free input' but does not explain any of the parameters, their roles, required combinations, or how the service interprets them. The description adds almost no semantic value over the sparse 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 identifies a specific action and resource: 'Person enrichment'. It also distinguishes itself from sibling enrichment tools like company_enrichment_evidence and contact_enrichment_evidence by naming 'person' as the subject. However, the phrase is somewhat jargon-heavy and doesn't fully explain what 'enrichment evidence' means in practice.

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?

There is no guidance about when to use this tool versus alternatives. It does not mention exclusions, prerequisites, or conditions that would route an agent to a different sibling tool. The only implicit hint is the word 'person', which is not enough for a tool with so many siblings.

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