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

Annotations already declare readOnlyHint/idempotentHint, and the description redundantly restates 'Read-only.' However, it goes beyond the annotations by teaching how to interpret and communicate results: naming the source (commissioned vs PlasticList-derived), preserving the four distinct measurement statuses, reporting sample counts, and avoiding unwarranted safety claims. It doesn't cover error or not-found behavior.

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?

Purpose and payload contents are front-loaded in the first sentence, with the delivery guidance second. It is dense but each clause carries distinct information; the final one-word 'Read-only' is redundant with annotations and is the only real waste.

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?

There is no output schema, so the description must describe the return shape — and it does thoroughly (provenance, samples with lot and analyses, per-analyte status/LOQ, exposure ratings). The main omission is behavior on invalid or unknown ids, which an agent would otherwise have to guess.

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% and the single id parameter's pattern and examples are fully documented in the schema, so the baseline is 3. The description only adds the provenance of the value ('from search_results'), with no format or constraint 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+resource ('Get the full public record for one result id') and explicitly scopes it to ids coming from the sibling search_results, so the agent can tell it apart from that tool. It also enumerates exactly what the record contains (provenance, samples, analytes, LOQ, exposure ratings), removing any ambiguity about the payload.

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?

The phrase 'one result id from search_results' clearly implies the search-then-fetch workflow and enough context to know when to call it. It adds substantial interpretation guidance ('keep statuses distinct', 'do not call a product safe'), but never explicitly states exclusions or what to do if the id is invalid/not found.

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