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

No annotations are provided, so the description carries the full burden. It does disclose two real behavioral traits: results are bounded to the supplied sources (no external lookup) and missing facts are reported explicitly rather than silently omitted, plus a per-call cost of 0.008 USDC. It says nothing about permissions, failure modes, or result shape, which leaves a mutation-free but still opaque contract.

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?

It is a single compact sentence with the scope stated first, which is structurally sound. But the brevity comes at the cost of comprehensibility: three dense compound modifiers and an embedded price are packed into one fragment, so it is terse rather than economical.

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 a tool with a nested object parameter, 0% schema coverage, no annotations, and no output schema, the description is far too thin. It should at minimum explain what 'subject' expects, how 'expected_fields' drives the coverage report, and what the missing-facts output looks like.

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 0% for three parameters, one of them a nested 'subject' object, and the description only obliquely gestures at 'source_urls' (source-bounded) and 'expected_fields' (field coverage). The maxItems constraints (5 sources, 32 fields), the required status of source_urls, and the internal structure of 'subject' are nowhere explained.

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 phrase 'entity field coverage with explicit missing facts' does convey that the tool reports which entity fields are supported by the given sources and flags gaps, and 'source-bounded' sets the scope. However, it is jargon-heavy noun phrasing with no verb, and it never distinguishes itself from the sibling enrichment tools (company/person/contact_enrichment_evidence), so an agent must guess which enrichment variant applies.

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 when-to-use guidance, no prerequisites, and no named alternative among the many sibling enrichment/evidence tools. The only routing signal is the price tag, which does not tell an agent when this tool is the right choice over company_enrichment_evidence or social_source_evidence.

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