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

Annotations already cover the safety profile (readOnly, non-destructive, closed-world), so the description's job is to add context, and it does: it discloses the join fallback rule (dbGaP study record or an identical-title RePORTER project), the specific rule-status semantics (BIOSECURE no-grace, UFLPA import presumption since Oct 29 2026), and the fact that the call is free. What it does not disclose is result volume or whether the set is exhaustive/paginated, so it is short of a 5.

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 dense sentence, but the scope-defining clause (dbGaP + BGI/MGI instruments) comes first and the enrichment fields follow, so it is well front-loaded. The parenthetical enumerations (DNBSEQ/BGISEQ/MGISEQ, BIOSECURE/UFLPA) add precision rather than filler, though the run-on construction is heavier than it needs to be.

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 no parameters, the description carries the full burden of explaining what comes back, and it enumerates the returned fields (grant join, grantee, PI, project end date, RePORTER award amounts, rule status). It also covers the tricky edge case of studies without a direct grant link via the identical-title RePORTER fallback. Nothing an agent needs in order to decide to call and interpret it is missing.

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?

The tool takes zero parameters, so the baseline of 4 applies; there is nothing for the description to clarify beyond confirming that the call is unfiltered and returns the full curated set. Saying it is 'Free' and param-free reinforces that it is a one-shot fetch rather than a filtered query.

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 pins down a very specific resource: dbGaP controlled-access human studies whose ENA sequencing runs were on BGI/MGI instruments, joined to their NIH grant and enriched with grantee, PI, end date, award amounts and rule status. An agent can tell this apart from generic exposure_awards or exposure_institution siblings by the instrument-vendor filter and the BIOSECURE/UFLPA rule-status payload. It lacks an explicit verb ('list'/'return'), but the noun phrase is precise enough to remove ambiguity.

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 explicit when-to-use or when-not-to-use statement and no sibling is named as an alternative, so routing between this and the other exposure_* tools is left to inference from the narrow scope. The trailing 'Free.' does signal a cost trade-off that matters when choosing among tools, which is a small but real usage hint. Usage is therefore implied rather than guided.

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