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 access filtering ('that you can read') and the shape of the result (included read in full vs. from abstract, or each screening decision with its reason), which is real behavioral context. However, it says nothing about pagination, result limits, or what happens when multiple reviews match.

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?

A single dense sentence, front-loaded with the core question ('Which ingested reviews ... include or screened a study'). The em-dash parentheticals are slightly awkward to parse but every clause earns its place.

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, the description must explain return values, and it sketches them (inclusion status or screening decision plus reason). It also covers input constraints, so an agent has enough to call it correctly; remaining gaps are pagination and multi-match behavior.

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%, so the description must compensate, and it largely does: it tells the agent the three lookup keys are DOI, PMID, or a title fragment, and adds the non-obvious 6+ character minimum for title matching. That is meaningful value beyond the bare 'Doi'/'Pmid'/'Title' field names, though it does not explain how the three are combined or prioritized.

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: find which ingested reviews include or screened a given study, and what happened to it in each. This is clearly distinct from sibling tools like synthscholar_studies or synthscholar_screening, though it never names those alternatives, so it falls short of a 5.

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 implied rather than stated: the reader infers this answers a cross-reference question about a single study. It gives format guidance for inputs (DOI, PMID, 6+ char title fragment) but never says when to prefer this over synthscholar_studies or synthscholar_records.

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