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

Annotations already cover the safety profile (readOnly, non-destructive, closed-world), and the description adds real value beyond them: it states there is no credit charge and no new research is triggered, and it explains the domain rule that a name/location is only a search hint and an identity without evidence is never a Match. It does not describe pagination or result volume, but for a read-only tool this is solid disclosure.

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 compact sentences, front-loaded with the return contents, followed by the domain caveats about identity evidence and the no-charge guarantee. Every sentence adds information; nothing is redundant, though the clauses are dense and slightly telegraphic.

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 single-parameter read-only tool with no output schema, the description does a reasonable job of describing what a response conceptually contains. However, it leaves find_id unexplained and gives no sense of result shape or size, which matters for a tool that returns per-row identities, sources, and namesakes.

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?

There is one required parameter (find_id) with 0% schema description coverage, so the description carries the full burden — yet it never mentions find_id or explains what identifier it expects. The phrase 'an imported list' hints that find_id selects the research, but an agent must infer that from the tool name rather than from the text.

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 uses a specific verb ('Reads') and enumerates exactly what is returned: each original row of an imported list, the identity decision with its source, unresolved namesakes, and the delivered record. This is clearly distinguishable from siblings like list_find_rows or get_find_decisions, 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 by the framing ('Review imported research' plus 'original row of an imported list'), with no statement of when to prefer this over get_find, get_find_decisions, or get_reconciled_input. The closing 'No charge and no new research' clarifies a constraint but is behavioral rather than routing guidance.

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